What is commit-push-pr?

A workflow for reviewing code changes, creating focused Git commits, pushing them to a remote repository, and opening a pull request for review.

Use it to inspect repository status, stage related files, write a semantic commit message, push the branch, and check whether a pull request already exists.

It organizes the steps between finishing a change and asking teammates to review it, while helping avoid mixing unrelated work.

commit-push-pr — Command for Claude Code by eddiebelaval/squire

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/eddiebelaval/squire

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/eddiebelaval/squire/commit-push-pr/github.svg)](https://agentmods.dev/commands/eddiebelaval/squire/commit-push-pr)

Your own site

<a href="https://agentmods.dev/commands/eddiebelaval/squire/commit-push-pr"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/commit-push-pr/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/eddiebelaval/squire/commit-push-pr"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/commit-push-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 602 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00602
Opus 5.5	$0.00000	$0.00241
Sonnet 5.5	$0.00000	$0.00120
Haiku 4.5	$0.00000	$0.00060

Measured 1mo ago against content hash 3c3ec894bc27, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

commit-push-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/commit-push-pr.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Commit, Push & Create PR

You are executing the commit-push-pr workflow - the most frequently used inner-loop command.

Pre-computed Context (inline bash for speed)

# Current state
BRANCH=$(git branch --show-current)
STATUS=$(git status --porcelain)
STAGED=$(git diff --cached --stat)
UNSTAGED=$(git diff --stat)
REMOTE_STATUS=$(git status -sb | head -1)
RECENT_COMMITS=$(git log --oneline -5)
PR_EXISTS=$(gh pr view --json number 2>/dev/null || echo "none")

Branch: $BRANCH Remote Status: $REMOTE_STATUS Staged Changes: $STAGED Unstaged Changes: $UNSTAGED Recent Commits: $RECENT_COMMITS Existing PR: $PR_EXISTS

User Intent

$ARGUMENTS

Workflow

Step 1: Analyze Changes

Review STATUS to understand what's changed
Identify logical groupings if multiple changes exist
Check if changes are related or should be separate commits

Step 2: Stage Appropriately

If user specified files, stage those
If no specification, stage all related changes
NEVER stage unrelated changes together

Step 3: Craft Commit Message

Follow semantic commit style:

feat: new feature
fix: bug fix
refactor: code restructuring
docs: documentation
test: adding tests
chore: maintenance

Message format:

type: short description (imperative mood)

- Bullet points for details if needed
- Focus on WHY, not WHAT (the diff shows what)

Step 4: Commit & Push

git add [files]
git commit -m "message"
git push -u origin $BRANCH

Step 5: Create or Update PR

If PR_EXISTS is "none":

gh pr create --title "PR Title" --body "## Summary
- Key change 1
- Key change 2

## Test Plan
- [ ] How to verify this works

---
Generated with [Claude Code](https://claude.com/claude-code)"

If PR already exists, just push (PR auto-updates).

Step 6: Report

Output the PR URL and summary of what was done.

Error Handling

If push fails due to divergence: git pull --rebase origin $BRANCH first
If PR creation fails: check if branch is pushed, check gh auth status
If nothing to commit: report "No changes to commit"

Read the full file on GitHub · 93 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 93 lines · 0 tokens per session scan A 3c3ec894bc27

Subscribe to this mod's changes

commit-push-pr is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 602 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code Code review Commits Git and workflow agent-os ai-agent ai-development claude codebase-audit

commit-push-pr