Menu
Skill for reviewing Magic Modules schemas. Currently covers the Enum vs. String decision via the knowledge base.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
| name | schema-review |
| description | Skill for reviewing Magic Modules schemas. Currently covers the Enum vs. String decision via the knowledge base. |
schema-reviewNote to AI Agents: You MUST read the YAML frontmatter above first. Only read the rest of this file if the
descriptionmatches your current roadblock or required task.
magic-modules root directory.When adding a field that is defined as an Enum in the API, you must decide between Enum and String in Magic Modules. Read the knowledge entry .agents/knowledge/field/enums-vs-strings.md and apply its trade-off.
[!NOTE] This skill will be expanded over time with more schema review checklist items. The judgment content lives in .agents/knowledge/ — this skill references it and does not hold its own copy.