pr

A command that prepares a GitHub pull request, which is a request for teammates to review and merge code into a shared branch.

In plain words
What is it for?
Use it to review branch changes, prepare conventional commits, run validation for common project types, and create a pull request description.
Why use it?
It reduces the manual work of finding the base branch, checking commits, creating missing commits, and running project checks.

Command

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.

agentmods
npx agentmods add commands/bravew/trove/pr
Clone the repo
git clone --depth 1 https://github.com/bravew/trove
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 606 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00006 $0.00606
Opus 5 $0.00003 $0.00303
Sonnet 5 $0.00001 $0.00121
Haiku 4.5 $0.00001 $0.00061

Measured 3d ago against content hash e4974ec6dfba, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 3d 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/pr.md · 97 lines

How it starts

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

Create Pull Request

PR Title (if provided): $ARGUMENTS

Process

  1. Detect base branch and verify state

    git branch --show-current
    git status
    
    # Fetch known integration branches
    git fetch origin --no-tags 2>/dev/null
    
    BASE=staging
    best_distance=""
    for candidate in staging production main master develop; do
      mb=$(git merge-base HEAD "origin/$candidate" 2>/dev/null) || continue
      distance=$(git rev-list --count "$mb"..HEAD 2>/dev/null) || continue
      if [[ -z "$best_distance" ]] || [[ "$distance" -lt "$best_distance" ]]; then
        best_distance=$distance
        BASE=$candidate
      fi
    done
    echo "Detected base branch: $BASE"
    
  2. Review changes

    git diff $BASE...HEAD --stat
    git log $BASE..HEAD --oneline
    
  3. Ensure commits are ready

    • Stage any uncommitted changes if needed
    • Create atomic commits with conventional commit messages
  4. Run validation using project-appropriate tools:

    Stack Commands
    Python ruff check . && ruff format --check . && pytest -v
    Node/React/Vue pnpm lint && pnpm type-check && pnpm test:run && pnpm build
    Next.js npm run lint && npm run type-check && npm run build
    Swift swift build && swift test
  5. Push to remote

    git push -u origin HEAD
    
  6. Create PR targeting the detected base branch

    gh pr create --base "$BASE" --title "<title>" --body "$(cat <<'EOF'
    ## Summary
    [Brief description of what this PR does]
    
    ## Changes
    - [List key changes with file references]
    
    ## Testing
    
    **Automated:**
    - [ ] Lint/format passes
    - [ ] Type checking passes
    - [ ] Tests pass
    - [ ] Build succeeds
    
    **Manual:**
    - [ ] [Specific flow tested]
    - [ ] Manual testing completed
    
    ## Breaking Changes
    [List any breaking changes or "None"]
    
    ## Checklist
    - [ ] Code follows project conventions
    - [ ] Self-reviewed
    - [ ] Tests added/updated
    EOF
    )"
    

Read the full file on GitHub · 97 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.

  1. 3d ago First seen · 97 lines · 6 tokens per session scan A e4974ec6dfba

Subscribe to this mod's changes

pr is a command published in the GitHub repository bravew/trove (10 stars, last pushed 4d ago), licensed MIT. It adds 6 tokens to every session and 606 once invoked, about $0.0000 per session on Opus 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-31.