What is commit-push-pr?

A command that completes a Git change workflow: it stages files, creates a conventional commit, pushes the branch, and opens a pull request. Git is a system for tracking code changes, and a pull request is a proposed change for review.

Preparing a branch for review, writing a commit message, pushing it to a remote repository, and creating a GitHub pull request.

It combines several repetitive release steps and creates a structured summary of what changed and how it was tested.

How llcoolblaze/claude-boris configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to llcoolblaze/claude-boris. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/llcoolblaze/claude-boris/main/.claude/commands/commit-push-pr.md

Clone the repo

git clone --depth 1 https://github.com/llcoolblaze/claude-boris

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/llcoolblaze/claude-boris/commit-push-pr/github.svg)](https://agentmods.dev/commands/llcoolblaze/claude-boris/commit-push-pr)

Your own site

<a href="https://agentmods.dev/commands/llcoolblaze/claude-boris/commit-push-pr"><img src="https://agentmods.dev/badge/commands/llcoolblaze/claude-boris/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/llcoolblaze/claude-boris/commit-push-pr"><img src="https://agentmods.dev/badge/commands/llcoolblaze/claude-boris/commit-push-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 340 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.00021	$0.00340
Opus 5.5	$0.00008	$0.00136
Sonnet 5.5	$0.00004	$0.00068
Haiku 4.5	$0.00002	$0.00034

Measured 2mo ago against content hash 75eca3a65078, 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 2mo 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.

.claude/commands/commit-push-pr.md · 55 lines

What it actually says

Git Context

!git status --short !git branch --show-current !git log -3 --oneline !git diff --stat

Based on the changes above, execute the full git workflow:

1. Stage Changes

Stage all modified files appropriately.

2. Commit

Create a commit with a conventional commit message:

feat: - New feature
fix: - Bug fix
docs: - Documentation only
style: - Formatting, no code change
refactor: - Code change that neither fixes nor adds
perf: - Performance improvement
test: - Adding tests
chore: - Maintenance, deps, config

Format: type(scope): description

Keep the first line under 72 characters. Add a body if the change needs explanation.

3. Push

Push to the remote repository. Create the remote branch if needed.

4. Create PR

Use gh pr create to open a pull request with:

Clear, descriptive title
Body explaining what changed and why
Link to related issues if applicable

gh pr create --title "type(scope): description" --body "## Summary
- What was done
- Why it was done

## Testing
- How it was tested

## Related
- Closes #123 (if applicable)"

If there are no changes to commit, inform the user and suggest next steps.

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.

2mo ago First seen · 55 lines · 21 tokens per session scan A 75eca3a65078

Subscribe to this mod's changes

commit-push-pr is a command published in the GitHub repository llcoolblaze/claude-boris (49 stars, last pushed 9mo ago), licensed MIT. It adds 21 tokens to every session and 340 once invoked, about $0.0001 per session on Opus 5.5. 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.

Commits Git and workflow

claude-boris: Command for Claude Code