.github/skills/docs-resource-sync/SKILL.md
Ensure documentation files under docs/resources/ and docs/data-sources/ reflect current resource types with accurate examples. Triggers on: after adding/updating resources, documentation audit.
npx skillsauth add aztfmod/terraform-provider-azurecaf docs-resource-syncInstall 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.
python3 -c "
import json
with open('resourceDefinition.json') as f:
resources = json.load(f)
print(f'Total resources: {len(resources)}')
# Count by category
categories = {}
for r in resources:
prefix = r['name'].replace('azurerm_', '').split('_')[0]
categories[prefix] = categories.get(prefix, 0) + 1
for cat, count in sorted(categories.items(), key=lambda x: -x[1])[:20]:
print(f' {cat}: {count}')
"
Read the current documentation files:
docs/resources/azurecaf_name.md — main resource documentationdocs/data-sources/azurecaf_name.md — data source documentationdocs/index.md — provider indexVerify:
resourceDefinition.jsonIf the docs include a resource type listing (table or details block), update it to match the current resourceDefinition.json entries. Include:
Check that example Terraform configurations in docs use valid resource types and produce valid outputs:
resourceDefinition.jsonDocs sync complete:
- docs/resources/azurecaf_name.md: <updated|current>
- docs/data-sources/azurecaf_name.md: <updated|current>
- docs/index.md: <updated|current>
- Resource count in docs: <count>
development
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.