.github/skills/issue-to-resource-spec/SKILL.md
Parse a 'new resource request' GitHub issue and extract the resource type, slug, and naming constraints to produce a draft resourceDefinition.json entry. Triggers on: issue labeled 'feature' or 'new-resource', new resource request.
npx skillsauth add aztfmod/terraform-provider-azurecaf issue-to-resource-specInstall 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.
Extract from the issue title and body:
azurerm_container_app)If the issue does not provide complete naming constraints, use the azure-naming-research skill procedure:
Using the researched values, format a complete JSON entry following the resource-definition-json skill's Format rules:
{
"name": "<resource_name>",
"min_length": <number>,
"max_length": <number>,
"validation_regex": "\"^<pattern>$\"",
"scope": "<scope>",
"slug": "<caf_abbreviation>",
"dashes": <true|false>,
"lowercase": <true|false>,
"regex": "\"[^<allowed_chars>]\"",
"official": {
"slug": "<caf_abbreviation>",
"resource": "<Official resource display name>",
"resource_provider_namespace": "<Microsoft.Provider/resourceType>"
}
}
Present the draft entry and a summary:
Resource: <resource_name>
Slug: <slug>
Length: <min>-<max>
Scope: <scope>
Status: Ready for implementation
This output can be used directly by the caf.add-resource agent.
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.