magic-modules

Skill for reviewing Magic Modules schemas. Currently covers the Enum vs. String decision via the knowledge base.

Opt resource into MMv1 list-resource generation by setting `generate_list_resource: true`, validate it locally, and open a one-resource PR against GoogleCloudPlatform/magic-modules. Invoke when the user asks to add list-resource support for a specific MMv1 resource or to enable `generate_list_resource` for an eligible resource.

Fallback workflow for general implementation and debugging tasks that do not involve creating a new resource.

Workflow specifically for creating a new resource, supporting both autogen and manual generation.

Create a Pull Request (PR) against GoogleCloudPlatform/magic-modules following repository standards, including branch management, commit formatting, mandatory release notes, pre-PR verification checks, and gh CLI commands.

Validate that changes to the generated providers don't introduce breaking changes or fields with missing tests or missing documentation. Use this skill when the user wants to check for breaking changes, missing tests, or missing documentation, or other problems in the downstream providers.

Guide for Phase 6 of TGC Main Loop (Fix). Use to understand how to fix failures.

Add a new field to an existing handwritten resource in TGC. Use when you need to extend a handwritten resource.

Add a new generated resource to TGC. Use when you need to add a new generated resource to TGC.

Add a new handwritten resource to TGC. Use when you need to add a new handwritten resource to TGC Next.

Build TGC from magic modules. Use when you need to build TGC from magic modules.

Create a pull request for Magic Modules changes to support a TGC feature, adhering to upstream conventions, prefixing with tgc-revival, and formatting empty release notes.

Fix integration tests for handwritten resources in TGC. Use when you need to fix integration tests for TGC.

Fix integration tests for TGC. Use when you need to fix integration tests for TGC.

Run integration tests for TGC. Use when you need to run integration tests for TGC.

Synchronize a downstream Terraform provider repository with Magic Modules by aligning commit history and verifying parity.

Triggers the QA Test Runner subagent to reproduce failures and interpret logs.

Parses massive Terraform debug logs into an easy-to-read outline of API delays, failures, and request payloads.

Executes code generation from Magic Modules into downstream Terraform providers and optionally compiles the binary.

Plan a remediation strategy after a test failure.

Checks sync status and invokes the subagent to align repositories if needed.

Gather context on a change or bug and plan the implementation.

Checks if the downstream provider repository is aligned with the correct Magic Modules base commit.

Configures Terraform CLI with developer overrides to test locally built provider binaries without full Go acceptance tests, enabling rapid plan/apply cycles.

Executes acceptance tests (testacc) for a specific resource or suite in the provider and outputs verbose debug logs.

Synchronize a downstream Terraform provider repository with Magic Modules by aligning commit history and verifying parity.

Verify if an MMv1 YAML property matches the live GCP REST API JSON payload using the Discovery Documents.