.github/skills/azure-resource-discovery/SKILL.md
Discover new Azure resources by fetching the latest azurerm provider resource list from the Terraform Registry and comparing against resourceDefinition.json. Identifies unsupported resources. Triggers on: weekly scheduled discovery, manual audit.
npx skillsauth add aztfmod/terraform-provider-azurecaf azure-resource-discoveryInstall 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.
Use Terraform MCP tools (get_provider_capabilities) to list all resources in the azurerm provider:
provider_name: azurerm
provider_namespace: hashicorp
provider_document_type: resources
Alternatively, query the Terraform Registry API:
curl -s "https://registry.terraform.io/v1/providers/hashicorp/azurerm" | python3 -c "
import json, sys
data = json.load(sys.stdin)
print(json.dumps(data, indent=2))
"
grep '"name":' resourceDefinition.json | sed 's/.*"name": "//;s/".*//' | sort > /tmp/ard-supported.txt
# Identify resources in azurerm but not in our provider
comm -23 /tmp/ard-azurerm.txt /tmp/ard-supported.txt > /tmp/ard-missing.txt
# Count
MISSING=$(wc -l < /tmp/ard-missing.txt)
SUPPORTED=$(wc -l < /tmp/ard-supported.txt)
Group missing resources by Azure service category:
## Azure Resource Discovery Report
### Summary
- azurerm provider resources: <total>
- Supported in CAF provider: <supported>
- Missing from CAF provider: <missing>
- Coverage: <percentage>%
### Missing Resources by Category
#### Compute (<count>)
- `azurerm_<resource>` — <description if available>
#### Storage (<count>)
- `azurerm_<resource>`
...
### Priority Recommendations
Resources that should be added first (commonly used, well-documented):
1. `azurerm_<resource>` — <reason>
2. ...
rm -f /tmp/ard-*.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.