.github/skills/resource-bulk-import/SKILL.md
Accept a list of Azure resource types, batch-research each via azure-naming-research conventions, generate JSON entries, and insert all into resourceDefinition.json. Triggers on: batch resource addition, bulk import requests.
npx skillsauth add aztfmod/terraform-provider-azurecaf resource-bulk-importInstall 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.
The caller provides a list of resource type names (e.g., azurerm_container_app, azurerm_container_registry).
for RESOURCE in <list>; do
if grep -q "\"name\": \"$RESOURCE\"" resourceDefinition.json; then
echo "SKIP: $RESOURCE (already exists)"
else
echo "ADD: $RESOURCE"
fi
done
For each resource to add, follow the azure-naming-research skill procedure:
Collect all results before making any edits.
For each researched resource, format the JSON entry following the resource-definition-json skill format rules. Present all entries to the user for review:
## Proposed Resources (<count>)
| # | Resource | Slug | Length | Scope | Dashes | Lowercase |
|---|----------|------|--------|-------|--------|-----------|
| 1 | <name> | <slug> | <min>-<max> | <scope> | <yes/no> | <yes/no> |
...
After user confirmation, insert all entries into resourceDefinition.json:
nameAfter inserting all entries, run a single build/test cycle:
go generate
make build
This is more efficient than building after each individual insertion.
## Bulk Import Complete
Added: <count> resources
Skipped: <count> (already existed)
Build: PASSED / FAILED
Tests: PASSED / FAILED
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.