gjoranv/claude-plan-skills / gh-create-pr
gh-create-pr
VerifiedCreate a GitHub PR from the current branch. Use when the user asks to "create a PR", "open a pull request", or "submit a PR".
Create GitHub pull request(s) from the current branch. If this session touched multiple repos (check conversation context, plan issue, or ask the user), create a PR in each repo. Run steps 1-7 for each repo in sequence.
- Check state: Run
git statusandgit branch --show-current. - Prepare a branch:
- Always fetch the latest base branch (main/master) first.
- If the current branch is main/master, create a new branch off the freshly fetched base. Pick a short, descriptive branch name from the conversation context (e.g.
resource-tags-docs). Move any uncommitted changes to the new branch. - Otherwise, rebase the current branch onto the freshly fetched base. If there are conflicts, stop and ask the user to resolve them.
- Handle uncommitted changes: If there are uncommitted changes on the (now non-master) branch, ask the user if they want to commit first. Do not proceed until the working tree is clean.
- Check for leaked references: Grep the diff and commit messages on this branch for references that the PR's audience cannot see: issues in a personal plan repo, internal issue trackers, or internal URLs. If found, warn the user and fix before proceeding.
- Push the branch: Push the current branch to remote with
git push -u origin. - Gather context: Read the git log for all commits on this branch since it diverged from the base branch. If a plan issue was referenced in this conversation, read it for additional context. Check for a PR template at
.github/pull_request_template.mdor.github/PULL_REQUEST_TEMPLATE.mdin the repo. If one exists, use it as the structure for the PR description. - Create the PR: Always use
gh pr create --web --title <title> --body <body>. The--webflag is mandatory; it opens the browser so the user can review and edit before submitting. Do not use--edit(terminal editor, unreliable). Do not omit--web.- A concise title (under 70 characters)
- Body: for trivial PRs (single commit, simple change), a few plain-text sentences covering what, why, and how it was tested. For non-trivial PRs (multi-commit, multi-file, or complex changes), use three sections:
## What,## Why,## Tested. Use bullet lists when listing multiple changes or test steps. Keep each section concise; reviewers read the diff for details.- For a long description, start with a brief TL;DR stating the change and its purpose.
## Testedholds only what has already been verified: tests run, a plan reviewed, a local deploy. Checks that can only happen once the change is merged or applied (a deploy, atofu apply, a rollout) go in a separate## Verify after mergesection, each saying what to look at; for infrastructure that takes effect on apply, say so in the check. Leave that section out when there is nothing to verify later.- Size the body to the change's consequence, not to the work behind it: a comment-only fix stays trivial however much investigation established it, while a one-line change to a widely-instantiated module is not.
- Lead with what the change does for the reviewer rather than the method that found it, and leave evidence, log excerpts and ruled-out hypotheses in the plan issue.
- Do not restate what the commit messages already say. The PR body adds the overarching why and how it was tested; the per-commit details are in the commits.
- For a large PR whose commits form a useful review sequence, add a line just before
## What, after any TL;DR, suggesting a commit-by-commit review.
- Link to the plan issue only if it is in the same repo as the PR. Never link to a plan issue in a personal or private repo from a PR in another repo. This applies to the PR description, comments, and commit messages.
- For PRs to public repos: never reference internal issue trackers or internal URLs.
- Do not set reviewers or labels when creating the PR; request a Copilot review afterwards when applicable (step 8).
- Footer: Check for
~/.claude/skills/gh-create-pr/pr-footer.md. If it exists, append its content to the PR body, separated by---. Replace{{model}}with the model family, version, and variant without extras like context window size (e.g. "Opus 4.8", "GPT-5.6 Sol"). Never guess the model. In Claude Code, take it from the system prompt. In Codex, look it up withsqlite3 ~/.codex/state_5.sqlite "SELECT model FROM threads WHERE id = '$CODEX_THREAD_ID'"and write the result as family, version, and variant (gpt-6-astra-> "GPT-6 Astra"). For non-public repos only, append an HTML comment with session metadata after the footer text (invisible in rendered view):<!-- session: <name> | dir: <directory> | model: <model> | id: <session-id> -->. Never add this to PRs in open source repos.
- Post-creation: The PR is created in the browser, so first ask the user to say when it is submitted. Then find the PR with
gh pr view --json number,urlon the branch and report its number and URL, so the session knows it exists; if there is none, the form was not submitted, so say so. For a non-trivial PR, ask whether to request a Copilot review before asking anyone for a human review. If yes, rungh pr edit <NUMBER> --add-reviewer @copilot.- If creating PRs across multiple repos, cross-link them in each PR description (e.g. "Related: owner/other-repo#N"). Do NOT cross-link from a public repo to a non-public repo.
Rules:
- Never create a PR without pushing the branch first.
- Keep the description concise. No empty boilerplate sections.
- Do not make unverified claims in the PR body or commit messages (e.g. "no functional change", "backward compatible"). Skip claims that don't add value.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |