菜单
Plan a remediation strategy after a test failure.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | fix |
| description | Plan a remediation strategy after a test failure. |
fixUse this skill after the qa-test-runner subagent returns a failure report. Your job is to analyze the failure and propose a new fix strategy (Remediation Planning). Do NOT run generation or testing yourself.
Read the report returned by qa-test-runner. Compare findings against standard troubleshooting patterns (e.g. perpetual diffs, normalization issues).
Ask the user if they have a suggested change, or if you should propose a new strategy from reference guides. Offer specific recommendations.
Once a solution is agreed upon, apply the change manually, and then transition back to Step 3 (Generate) to compile the fix.