Menu
Fallback workflow for general implementation and debugging tasks that do not involve creating a new resource.
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
| name | default-workflow |
| description | Fallback workflow for general implementation and debugging tasks that do not involve creating a new resource. |
default-workflowThis document outlines the structured 5-step lifecycle for formal implementation and debugging tasks in Magic Modules.
repo-sync skill (located in .agents/skills/operations/repo-sync/). This skill handles checking the sync status and prompting for action if needed..agents/knowledge/index.md for the topics the change touches and open the relevant sources.triage skill (located in .agents/skills/operations/triage/) to perform this work.generate-provider skill (located in .agents/skills/operations/generate-provider/) to compile machine code in the downstream.qa-test-runner subagent using the invoke_subagent tool to reproduce failures and interpret logs. The subagent evaluates if the test fails/passes and returns a human-readable interpretation of the results.qa-test-runner and compare against reference guides or user suggestions. Propose a specific fix code change to the user.fix skill (located in .agents/skills/operations/fix/) to perform this planning.Repeat steps 2-5 as needed during the session until the primary task is complete. Reset to Step 3 (Generate) after applying an approved fix to compile it!
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.
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.