菜单
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.
用 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 | tgc-create-pr-skill |
| description | 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. |
tgc-create-pr-skillNote 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.mmv1/ ready to be committed and pushed.gh CLI installed and authenticated on the host machine.Verify that only files inside the mmv1/ folder are modified or staged. Ensure no scratch files, text files, or downstream TGC files are modified.
# Run in magic-modules root directory
git status
[!IMPORTANT] If any files outside the
mmv1/directory (e.g., downstream files,.txt,.sh, or.pyscripts) are staged or tracked, you MUST reset them before committing.
Ensure your local git repository is aware of the latest upstream/main changes before branching.
git fetch upstream main
Create and checkout a new local feature branch based on the fetched upstream/main (or FETCH_HEAD).
git checkout -b tgc-<feature-name> upstream/main
Verify that your uncommitted/staged mmv1/ changes have successfully carried over to the new branch.
Stage and commit the mmv1/ changes with a clear, descriptive commit message.
git add mmv1/...
git commit -m "[TGC] Support <feature_name> in <resource_name>"
Push the local branch to your GitHub fork (origin).
git push -u origin tgc-<feature-name>
Check that the GitHub CLI is logged in and active.
gh auth status
Create the pull request to the GoogleCloudPlatform/magic-modules upstream repository. Ensure the title is prefixed with tgc-revival: and the body includes the standard empty release note block.
gh pr create \
--base main \
--title "tgc-revival: Support <field/resource> in <ResourceName>" \
--body "Support GKE <field/resource> in <ResourceName>
\`\`\`release-note:none
\`\`\`"
gh pr create command, copy the returned pull request URL and print it for the user.task.md to mark pull request creation and commit as fully completed.