Borrowing it
Nothing to install: this file belongs to tomdwipo/claude-soul. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tomdwipo/claude-soul/main/.claude/commands/push-pr.mdgit clone --depth 1 https://github.com/tomdwipo/claude-soulWrote 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.
[](https://agentmods.dev/commands/tomdwipo/claude-soul/push-pr)<a href="https://agentmods.dev/commands/tomdwipo/claude-soul/push-pr"><img src="https://agentmods.dev/badge/commands/tomdwipo/claude-soul/push-pr.svg" alt="Measured on agentmods" height="20"></a>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.01110 |
| Opus 5 | $0.00000 | $0.00555 |
| Sonnet 5 | $0.00000 | $0.00222 |
| Haiku 4.5 | $0.00000 | $0.00111 |
Grade A, and why
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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Push and PR Command
Execute the complete PR workflow: commit all changes, push to remote, create PR, and transition Jira ticket.
Arguments Format
$ARGUMENTS = <target-branch> [ticket-id] [reviewers]
Examples:
/push-pr epic/PROJ-1234- Auto-detect ticket from current branch/push-pr epic/PROJ-1234 PROJ-1240- Explicit ticket override/push-pr epic/PROJ-1234 PROJ-1240 alice,bob- With reviewers
Workflow Steps
Step 1: Parse Arguments
Extract from $ARGUMENTS:
- target-branch (required): The destination branch for PR (e.g.,
epic/PROJ-1234,master) - ticket-id (optional): Jira ticket ID. If not provided, extract from current branch name (e.g.,
task/PROJ-1240→PROJ-1240) - reviewers (optional): Comma-separated list of reviewer names
Step 2: Git Status Check
Run git status to verify there are changes to commit. If no changes, skip to PR creation if branch has unpushed commits.
Step 3: Commit All Changes
- Run
git add -Ato stage all changes - Generate commit message based on:
- Jira ticket ID
- Summary of changed files
- Use format:
feat(<module>): <description>
- Commit with a Conventional Commit message (no AI/tool attribution trailer)
Step 4: Push to Remote
Run git push -u origin <current-branch> to push changes to remote.
Step 5: Create Pull Request
Use Bitbucket MCP tool to create PR:
- workspace:
<your-workspace> - repoSlug:
<your-repo> - sourceBranch: Current branch
- destinationBranch: Target branch from arguments
- title: Same as the commit message
- description: Include Jira link, summary, and test plan
Missing Figma references hook — before composing the description, grep the
staged AC.md for a ### Figma Reference Notes section. If present and it
contains any ⚠️ lines, copy them verbatim into the PR description under a
## Missing Figma References heading (place it BEFORE the test plan so the
reviewer sees it on first scroll). Each line names the screen, state, reason,
and Figma URL (when known) so the reviewer can open Figma directly. If the
section is empty or absent, omit the heading entirely — do not insert an
empty block.
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.
- 8d ago First seen · 109 lines · 0 tokens per session scan A 937b1ff478d4
push-pr is a command published in the GitHub repository tomdwipo/claude-soul (24 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,110 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.
Other commands, from other repositories
gsd:quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
backlog-git
Control de versiones para backlogs de proyectos.
company-repo
Gestionar el repositorio Company Savia: crear, conectar, estado, sincronizar. El repositorio compartido de la empresa para conocimiento, mensajería y estado.
gsd:pause-work
Create context handoff when pausing work mid-phase.
gsd:remove-phase
Remove a future phase from roadmap and renumber subsequent phases.
weekly-summary
Generate weekly work summary from git activity.