sova: Command for Claude Code

.claude/commands/pr.md

pr is a command for Claude Code from xsovad06/sova. It costs 21 tokens per session (7,760 once invoked), scanned A, original, Apache-2.0.

A command that prepares a pull request, which is a request to merge code changes into a shared branch. It reviews the branch’s commits and changes and follows the project’s standard template.

In plain words
What is it for?
Use it to update and rebase a feature branch, inspect its changes, handle conflicts, and create a pull request with the relevant project information.
Why use it?
It helps bring the branch up to date and avoid an unclear or incorrectly scoped merge request.

Command for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions CLAUDE.md.

This is xsovad06/sova's own configuration. It tells Claude Code how to work on sova itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything sova configures →

Reuse

Borrowing it

Nothing to install: this file belongs to xsovad06/sova. 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/xsovad06/sova/main/.claude/commands/pr.md
Clone the repo
git clone --depth 1 https://github.com/xsovad06/sova

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.

agentmods badge for pr

README.md
[![agentmods](https://agentmods.dev/badge/commands/xsovad06/sova/pr/github.svg)](https://agentmods.dev/commands/xsovad06/sova/pr)
Your own site
<a href="https://agentmods.dev/commands/xsovad06/sova/pr"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/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.

agentmods 80×15 button for pr

Your own site · 80×15
<a href="https://agentmods.dev/commands/xsovad06/sova/pr"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/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 7,760 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.07760
Opus 5.5 $0.00008 $0.03104
Sonnet 5.5 $0.00004 $0.01552
Haiku 4.5 $0.00002 $0.00776

Measured 4d ago against content hash 99789cf1109e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 4d 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/pr.md · 396 lines

How it starts

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

Create Pull Request

Create a pull request for the current branch using the project's standard PR template.

Instructions

  1. Resolve the base branch and fetch (do not rebase yet: step 3 decides whether rebasing is safe for this PR): Resolve the base branch at runtime rather than assuming main. Every shell block in this command runs in a fresh shell, so each block that uses BASE re-assigns it first. Fall back to the repo default only when gh pr view confirms there is no PR for this branch yet; abort on any other failure (auth, network, API) instead of guessing:

    BASE=$(gh pr view --json baseRefName --jq .baseRefName 2>&1) || { case "$BASE" in *"no pull requests found"*) BASE=$(gh repo view --json defaultBranchRef --jq .defaultBranchRef.name) ;; *) echo "Unable to resolve the base branch: $BASE" >&2; exit 1 ;; esac; }
    [ -n "$BASE" ] || { echo "Unable to resolve the base branch" >&2; exit 1; }
    git fetch origin || { echo "Fetch failed: STOP, origin/$BASE may be stale" >&2; exit 1; }
    echo "Base branch: $BASE"
    
    • Never check out the base branch: in a linked worktree it is usually checked out elsewhere, so git checkout "$BASE" fails. Rebase onto the remote-tracking ref instead.
    • Verify the GitHub account: gh auth status must show the account the project configures as its GitHub user (for SOVA projects, sova config get github_user prints it). Otherwise --assignee @me in step 11 assigns the wrong user and later thread writes fail with FORBIDDEN. If it differs, run gh auth switch --user <github_user>.
  2. Gather branch information. These commands do not need $BASE and can run in parallel:

    • git status: check for uncommitted changes
    • git branch --show-current: get current branch name
    • git diff --stat: summary of uncommitted changes
    • gh pr list --head $(git branch --show-current) --json number,url,state: check if PR already exists

    The two commands below need $BASE, resolved fresh in this shell (same fail-closed resolution as step 1):

    BASE=$(gh pr view --json baseRefName --jq .baseRefName 2>&1) || { case "$BASE" in *"no pull requests found"*) BASE=$(gh repo view --json defaultBranchRef --jq .defaultBranchRef.name) ;; *) echo "Unable to resolve the base branch: $BASE" >&2; exit 1 ;; esac; }
    [ -n "$BASE" ] || { echo "Unable to resolve the base branch" >&2; exit 1; }
    git log "origin/$BASE"..HEAD --oneline
    git diff "origin/$BASE"...HEAD --stat
    

Read the full file on GitHub · 396 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. 4d ago Changed · +3 lines 99789cf1109e
  2. 5d ago Changed · +66 lines 7cd58624135b
  3. 6d ago Changed · +50 lines 4b6e029acb43
  4. 9d ago Changed · +14 lines 664a7c2598e9
  5. 14d ago Changed · +8 lines 5f079244d802
  6. 16d ago Changed · +48 lines 49c4a74c5ad0
  7. 19d ago Changed · +1 lines 6a35ad47d3e9
  8. 21d ago Changed 2dd7aad50e5d
  9. 22d ago Changed 5f250cb5970a
  10. 1mo ago First seen · 206 lines · 21 tokens per session scan A 4e1fa1367abd

Subscribe to this mod's changes

pr is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 21 tokens to every session and 7,760 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-31.