.github/skills/resource-completeness-check/SKILL.md
Compare resourceDefinition.json against completness/existing_tf_resources.txt to report coverage gaps. Shows which Terraform azurerm resources are supported and which are missing. Triggers on: audit, completeness review.
npx skillsauth add aztfmod/terraform-provider-azurecaf resource-completeness-checkInstall 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.
sort completness/existing_tf_resources.txt > /tmp/rc-reference.txt
wc -l /tmp/rc-reference.txt
grep '"name":' resourceDefinition.json | sed 's/.*"name": "//;s/".*//' | sort > /tmp/rc-supported.txt
wc -l /tmp/rc-supported.txt
# Missing (in reference but not supported)
comm -23 /tmp/rc-reference.txt /tmp/rc-supported.txt > /tmp/rc-missing.txt
# Extra (supported but not in reference — may be valid out-of-doc resources)
comm -13 /tmp/rc-reference.txt /tmp/rc-supported.txt > /tmp/rc-extra.txt
## Resource Completeness Report
### Summary
- Reference resources (existing_tf_resources.txt): <count>
- Supported in provider: <count>
- Missing: <missing_count>
- Coverage: <percentage>%
### Missing Resources (<count>)
| # | Resource |
|---|----------|
| 1 | `azurerm_<name>` |
| 2 | `azurerm_<name>` |
...
### Extra Resources (<count>)
Resources in provider but not in reference list (may be out-of-doc):
| # | Resource |
|---|----------|
| 1 | `azurerm_<name>` |
...
rm -f /tmp/rc-*.txt
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.