Stats
Actions
Tags
From claude-coding
Pushes commits, auto-creates feature branches from commit messages, and creates/updates GitHub pull requests using git and gh CLI. Manages clean trees and multi-PR splitting.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-coding:push-prThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Push commits and create/update pull requests with automatic branch management and
Push commits and create/update pull requests with automatic branch management and scope-aware multi-PR splitting.
Parse flexibly from $ARGUMENTS:
1=opened, 2=draft, 3=ready (default: new PR=opened, update=draft)main)Injected at invocation — analyze before taking any action:
!git status --porcelain!git rev-parse --abbrev-ref HEAD!git rev-list @{u}..HEAD --count 2>/dev/null || echo "no upstream"!git log origin/main..HEAD --oneline 2>/dev/null (assumes main base; see Step 3 if base differs)!git diff origin/main...HEAD --stat 2>/dev/null (captured before fetch; re-run if stale)Run git fetch origin to sync remote state.
If the working tree status above shows uncommitted changes, invoke Skill: commit to
commit first.
Complete when: remote is fetched and working tree is clean.
If on main/master with unpushed commits, cut a feature branch before proceeding.
Branch naming: prefix from the primary commit's conventional type (feat/, fix/,
docs/, chore/, refactor/); slug from the commit scope or subject, lowercase hyphens
only, max 45 chars total (keeps branch names readable in GitHub's UI and avoids truncation
in terminal prompts). Use the scope if present (feat(auth) → feat/auth); otherwise
condense the subject to 2–4 words (fix login redirect timeout → fix/login-redirect).
git checkout -b <derived-branch-name>
git branch -f main origin/main
git branch -f moves main's pointer back to origin/main without checkout or --hard —
non-destructive and never triggers permission denials.
If already on a feature branch: skip to step 3.
Complete when: HEAD is on a feature branch (not main/master).
Derive working variables from pre-flight context and arguments:
BASE = base-branch argument, or main if not providedBRANCH = current branch name (from pre-flight injection)Use the pre-flight context injected above. If the base branch differs from main,
re-gather against origin/$BASE:
git log origin/$BASE..HEAD --oneline --reverse
git diff origin/$BASE...HEAD --stat
Always compare against origin/$BASE, not local $BASE — the PR targets the remote
branch, so comparisons must match what GitHub will see.
Record: commit count, conventional-commit types and scopes present, total diff lines
(approximate from --stat output).
Complete when: commit count, scope/type inventory, and approximate diff size are known.
Evaluate whether the changeset warrants multiple PRs. A split is warranted when either:
feat(auth), fix(ui), chore(deps)) — multiple scopes mean the changeset lacks a
single narrative, making review harder and revert riskierIf neither condition is met: proceed to step 5 as a single PR.
If either condition is met — propose stacked PRs:
Cluster commits by scope/type in the order they were made. Each cluster becomes one PR
targeting the previous cluster's branch (the first targets $BASE). Present the plan:
Proposed stacked PRs (each PR targets the previous branch):
PR 1 [base: main] feat/auth — commits: abc1234, def5678
PR 2 [base: feat/auth] fix/ui-redirect — commits: ghi9012
PR 3 [base: fix/ui-...] chore/cleanup — commits: jkl3456
Use AskUserQuestion: "Split into N stacked PRs as shown above, or push as a single PR?"
If user declines split: proceed to step 5 as a single PR.
If user confirms split — stacked PR execution:
For each cluster in order:
$BASE for cluster 1):
git checkout -b <cluster-branch> <previous-branch>
git cherry-pick <sha1> <sha2> ...
git push -u origin <cluster-branch>--base <previous-branch>:
python3 ${CLAUDE_PLUGIN_ROOT}/skills/push-pr/scripts/format-pr-body.py --base "<previous-branch>"
After all PRs are created, check out the last cluster's branch and report the full stack (see Output). Exit — skip steps 5–7.
Complete when: user has chosen single-PR or stacked, and stacked flow is finished if chosen.
Check for an existing PR on this branch: gh pr list --head "$BRANCH" --json number,state
Use the provided status argument, or default: new PR=opened, update=draft.
Complete when: existing PR state is known and target status is determined.
Push the branch to origin. If no upstream is set, use git push -u origin "$BRANCH".
If push fails because the remote branch has diverged, run git pull --rebase origin $BRANCH
and retry the push once. If the rebase itself has conflicts, stop and report.
Complete when: branch is pushed and tracking the remote.
Generate the PR body using the format script:
python3 ${CLAUDE_PLUGIN_ROOT}/skills/push-pr/scripts/format-pr-body.py --base "origin/$BASE"
Exit 1 means no changes found relative to base; report to user. On success, use stdout as the PR body directly.
New PR:
gh pr create --title "<title>" --body "<format-pr-body output>" --base "$BASE"
# If status=ready: gh pr ready
Existing PR: Add a comment listing new commits since last push; update PR status if the status argument changed.
PR_NUM=$(gh pr list --head "$BRANCH" --json number -q '.[0].number')
gh pr comment $PR_NUM --body "New commits: ..."
Complete when: PR URL is obtained and status matches the target.
Produce clean, unattributed PRs that match the project's existing commit and PR style:
user.name or user.emailgit remote add origin <url> and stopgh CLI → report requirement and stopgit cherry-pick --abort followed by manual
resolution, then re-runningSingle PR: branch name, PR URL, PR status (opened/draft/ready).
Stacked PRs: ordered list showing each PR URL and the branch it targets, plus the name of the final branch now checked out.
npx claudepluginhub gupsammy/claudest --plugin claude-codingCommits changes to a new git branch (if on main), pushes to origin, and creates or views GitHub PR with gh CLI. Activates on 'commit and push', 'open PR', 'ship it'.
Creates new git branch if on main, commits and pushes changes, adapts PR template to git diffs, and opens GitHub pull request with conventional commit title.
Commits changes, pushes to a feature branch, and creates a PR for review. Handles branch detection, rebasing, and conventional commits.