.github/skills/contributor-guide/SKILL.md
Provide step-by-step guidance for contributors based on their contribution type. References CONTRIBUTING.md and project conventions. Triggers on: new contributor questions, 'how do I contribute', contribution guidance requests.
npx skillsauth add aztfmod/terraform-provider-azurecaf contributor-guideInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Ask the contributor (or infer from context) what they want to do:
| Type | Description | |------|-------------| | new-resource | Add a new Azure resource type to the provider | | update-resource | Update an existing resource's naming constraints | | bug-fix | Fix a bug in the provider logic | | docs | Improve documentation | | test | Add or improve tests |
For new-resource contributions:
grep '"name": "azurerm_<name>"' resourceDefinition.jsonazure-naming-research skill)resourceDefinition.json — add the entry in alphabetical ordergo generate && make build to regenerate code and testCHANGELOG.md under ## [Unreleased] → ### AddedREADME.md resource status table.github/PULL_REQUEST_TEMPLATE.mdFor update-resource contributions:
grep -A 15 '"name": "azurerm_<name>"' resourceDefinition.jsonresourceDefinition.jsongo generate && make buildCHANGELOG.md under ## [Unreleased] → ### ChangedFor bug-fix contributions:
make buildCHANGELOG.md under ## [Unreleased] → ### FixedFor docs contributions:
docs/ or README.mdPoint the contributor to:
.github/CONTRIBUTING.md for full guidelines.github/PULL_REQUEST_TEMPLATE.md for the PR checklistTESTING.md for test instructionsdevelopment
Analyze test failure output to identify root cause and suggest fixes. Use when build or test failures occur. Triggers on: test failures, build errors, CI failures.
development
Validate a resource definition end-to-end using terraform test with mock_provider azurerm. Proves the CAF-generated name is accepted by the azurerm provider schema without Azure credentials. Use after provider-build-test succeeds to run the mocked azurerm integration test.
documentation
Analyze changes since the last release tag and determine the appropriate semantic version bump (patch/minor/major) based on CHANGELOG entries and commit types. Triggers on: release preparation, version planning.
testing
Compare two versions of resourceDefinition.json (e.g., branch vs main) and produce a structured change summary. Triggers on: PR review, audit, before/after comparison.