Menu
Checks if the downstream provider repository is aligned with the correct Magic Modules base commit.
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
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 | check-sync-provider |
| description | Checks if the downstream provider repository is aligned with the correct Magic Modules base commit. |
check-sync-providerUse this skill to verify if the downstream repository is at the correct baseline commit before generating code or running tests.
GoogleCloudPlatform/magic-modules remote (usually upstream).main: Use current commit (HEAD).git merge-base HEAD <canonical-remote>/main to find where the branch diverged.HEAD of the downstream repository matches that found commit.