菜单
Regenerate Go code from resourceDefinition.json, build the terraform-provider-azurecaf binary, and run unit tests. Use after any change to resourceDefinition.json to verify the provider compiles and tests pass.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Fetch the latest CAF abbreviations page from Microsoft Learn and compare against resourceDefinition.json official.slug values. Reports drift where the provider's slug differs from the official CAF slug. Triggers on: weekly scheduled audit, manual sync check.
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.
Update CHANGELOG.md with a new entry under the correct section. Parses existing structure, adds entries under [Unreleased], and assesses semver impact. Triggers on: after resource changes, bug fixes, documentation updates, or any notable project change.
Provide step-by-step guidance for contributors based on their contribution type. References CONTRIBUTING.md and project conventions. Triggers on: new contributor questions, 'how do I contribute', contribution guidance requests.
Run test coverage analysis (make test_coverage), parse coverage percentage, compare against the 95% threshold, and flag regressions. Triggers on: PR checks, post-build validation, release prep.
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.
| name | provider-build-test |
| description | Regenerate Go code from resourceDefinition.json, build the terraform-provider-azurecaf binary, and run unit tests. Use after any change to resourceDefinition.json to verify the provider compiles and tests pass. |
Run from the project root after editing resourceDefinition.json:
go generate # regenerates azurecaf/models_generated.go
make build # runs go generate + go fmt + go build + go test
Verify the resource appears in generated code:
grep "<resource_name>" azurecaf/models_generated.go
Expected output: ok for all test packages, coverage ~90%+, no compilation errors.
If go generate fails: check JSON formatting (missing commas, unmatched quotes, bad escapes).
If tests fail: check for duplicate slugs causing ambiguity.