.github/skills/resource-definition-json/SKILL.md
Manage resource entries in resourceDefinition.json for the terraform-provider-azurecaf naming provider. Use for lookup, comparison, formatting, and insert/update of resource naming definitions. Triggers on: resourceDefinition.json edits, resource definition lookup, JSON entry formatting, resource comparison.
npx skillsauth add aztfmod/terraform-provider-azurecaf resource-definition-jsonInstall 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.
grep -n '"name": "<resource_name>"' resourceDefinition.json
If found, read ~15 lines to extract: name, min_length, max_length, validation_regex, scope, slug, dashes, lowercase, regex, official.slug, official.resource, official.resource_provider_namespace, out_of_doc.
If not found, also try azurerm_<resource_name>.
Present a comparison table:
| Field | Current | Expected | Status |
|-------|---------|----------|--------|
| slug | ... | ... | MATCH / MISMATCH |
Check all fields. Statuses: MATCH, MISMATCH, MISSING, UNKNOWN.
See references/json-format.md for the exact JSON entry template and formatting rules.
name fieldprovider-build-test skilldevelopment
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.