How do I install the Tgc Create Pr Skill skill?

Run npx skillmds@latest add googlecloudplatform/tgc-create-pr-skill in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Tgc Create Pr Skill safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Tgc Create Pr Skill?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Tgc Create Pr Skill free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Tgc Create Pr Skill?

GoogleCloudPlatform (@googlecloudplatform) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Tgc Create Pr Skill by googlecloudplatform

Name: Tgc Create Pr Skill
Author: GoogleCloudPlatform

File contents

`tgc-create-pr-skill`

Note to AI Agents: You MUST read the YAML frontmatter above first. Only read the rest of this file if the description matches your current roadblock or required task.

Prerequisites

You must be working in the magic-modules root directory.
You must have local changes inside mmv1/ ready to be committed and pushed.
You must have the gh CLI installed and authenticated on the host machine.

Execution Steps

1. Verification of Staged Changes

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 .py scripts) are staged or tracked, you MUST reset them before committing.

2. Fetching Upstream Baseline

Ensure your local git repository is aware of the latest upstream/main changes before branching.

git fetch upstream main

3. Creating a New Branch Based on 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.

4. Committing the Changes

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>"

5. Pushing the Branch

Push the local branch to your GitHub fork (origin).

git push -u origin tgc-<feature-name>

6. Verifying GitHub CLI Auth

Check that the GitHub CLI is logged in and active.

gh auth status

7. Creating the Pull Request

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
\`\`\`"

Verification & Handoff

Upon running the gh pr create command, copy the returned pull request URL and print it for the user.
Update task.md to mark pull request creation and commit as fully completed.

---name: tgc-create-pr-skilldescription: 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-skill`> **Note to AI Agents:** You MUST read the YAML frontmatter above first. Only read the rest of this file if the `description` matches your current roadblock or required task.## Prerequisites* You must be working in the `magic-modules` root directory.* You must have local changes inside `mmv1/` ready to be committed and pushed.* You must have the `gh` CLI installed and authenticated on the host machine.## Execution Steps### 1. Verification of Staged ChangesVerify that only files inside the `mmv1/` folder are modified or staged. Ensure no scratch files, text files, or downstream TGC files are modified.```bash# Run in magic-modules root directorygit status```> [!IMPORTANT]> If any files outside the `mmv1/` directory (e.g., downstream files, `.txt`, `.sh`, or `.py` scripts) are staged or tracked, you MUST reset them before committing.### 2. Fetching Upstream BaselineEnsure your local git repository is aware of the latest `upstream/main` changes before branching.```bashgit fetch upstream main```### 3. Creating a New Branch Based on Upstream MainCreate and checkout a new local feature branch based on the fetched `upstream/main` (or `FETCH_HEAD`).```bashgit checkout -b tgc-<feature-name> upstream/main```Verify that your uncommitted/staged `mmv1/` changes have successfully carried over to the new branch.### 4. Committing the ChangesStage and commit the `mmv1/` changes with a clear, descriptive commit message.```bashgit add mmv1/...git commit -m "[TGC] Support <feature_name> in <resource_name>"```### 5. Pushing the BranchPush the local branch to your GitHub fork (`origin`).```bashgit push -u origin tgc-<feature-name>```### 6. Verifying GitHub CLI AuthCheck that the GitHub CLI is logged in and active.```bashgh auth status```### 7. Creating the Pull RequestCreate 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.```bashgh pr create \ --base main \ --title "tgc-revival: Support <field/resource> in <ResourceName>" \ --body "Support GKE <field/resource> in <ResourceName>\`\`\`release-note:none\`\`\`"```## Verification & Handoff* Upon running the `gh pr create` command, copy the returned pull request URL and print it for the user.* Update `task.md` to mark pull request creation and commit as fully completed.

Frequently asked questions

Tgc Create Pr Skill