sova: Command for Claude Code

.claude/commands/rearrange-commits.md

rearrange-commits is a command for Claude Code from xsovad06/sova. It costs 23 tokens per session (2,502 once invoked), scanned A, original, Apache-2.0.

A Git workflow for reorganizing the commits on the current branch into small, logical steps. A commit is a saved snapshot of changes in Git.

In plain words
What is it for?
Use it to group schema, application logic, API, tests, and configuration changes into documented commits, then compare them with the main branch.
Why use it?
It makes a branch's history easier to review by separating unrelated changes and preserving a clear order.

Command for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: mentions AGENTS.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/rearrange-commits.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 rearrange-commits

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/xsovad06/sova/rearrange-commits"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/rearrange-commits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,502 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.00023 $0.02502
Opus 5.5 $0.00009 $0.01001
Sonnet 5.5 $0.00005 $0.00500
Haiku 4.5 $0.00002 $0.00250

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

Security

Grade A, and why

rearrange-commits 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 6d 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/rearrange-commits.md · 161 lines

How it starts

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

Rearrange Commits

Reorganize all commits on the current branch into clean, logical, atomic commits.

Instructions

Step 1: Analyze Current State

Resolve the base branch at runtime rather than assuming main. Every shell block runs in a fresh shell, so each block below 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; }
echo "Base branch: $BASE"
git fetch origin || { echo "Fetch failed: STOP, origin/$BASE may be stale" >&2; exit 1; }
git branch --show-current
git log "origin/$BASE"..HEAD --oneline
git diff "origin/$BASE"...HEAD --stat
git status

Step 2: Preserve All Changes

Never use git stash here: the stash stack is shared by every worktree and session of this repository, so a pop can restore someone else's changes. Commit uncommitted work instead, and keep a backup branch until the rearranged history is verified.

  1. Commit any uncommitted changes as a WIP commit (review git status first, so nothing that must not be committed, such as secrets or scratch files, is included):
    if [ -n "$(git status --porcelain)" ]; then
      git add -A && git commit -m "chore: WIP snapshot before rearrange" \
        || { echo "WIP commit failed (hook, signing or staging error): STOP, nothing was reset" >&2; exit 1; }
    fi
    
  2. Create a uniquely named backup branch and note the printed name, since later blocks re-assign BACKUP to it. The tree must be fully committed first, or the Step 4 recovery would drop the uncommitted work:
    [ -z "$(git status --porcelain)" ] || { echo "Uncommitted changes remain: STOP before creating the backup" >&2; exit 1; }
    BACKUP="backup/rearrange-$(date +%s)-$$-$RANDOM"
    git branch "$BACKUP" || { echo "Failed to create backup branch $BACKUP: STOP before resetting" >&2; exit 1; }
    echo "Backup branch: $BACKUP"
    
  3. Soft reset to the point where this branch forked from the base, and note the printed SHA. Use the fork point (git merge-base), not origin/$BASE itself: if the base branch moved since this branch was last rebased, committing the branch's tree on top of the newer base would silently revert everything the base gained in between.
    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; }
    FORK_POINT=$(git merge-base HEAD "origin/$BASE")
    echo "Fork point: $FORK_POINT"
    git reset --soft "$FORK_POINT"
    git reset HEAD .
    
    All changes, including the WIP snapshot, are now unstaged in the working tree.

Read the full file on GitHub · 161 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. 6d ago Changed · +24 lines 3f1a2c2d33e7
  2. 14d ago Changed · +3 lines 3336b08d7493
  3. 16d ago Changed · +45 lines 92e6ec31d7f0
  4. 1mo ago Changed 649f7adbe1a5
  5. 2mo ago First seen · 89 lines · 23 tokens per session scan A 7f44219243bf

Subscribe to this mod's changes

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