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.
curl -O https://raw.githubusercontent.com/xsovad06/sova/main/.agents/skills/source-command-rearrange-commits/SKILL.mdgit clone --depth 1 https://github.com/xsovad06/sovaWrote 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/skills/xsovad06/sova/source-command-rearrange-commits)<a href="https://agentmods.dev/skills/xsovad06/sova/source-command-rearrange-commits"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/source-command-rearrange-commits.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.00025 | $0.00551 |
| Opus 5 | $0.00013 | $0.00275 |
| Sonnet 5 | $0.00005 | $0.00110 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
source-command-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 yesterday.
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.
What it actually says
source-command-rearrange-commits
Use this skill when the user asks to run the migrated source command rearrange-commits.
Command Template
Rearrange Commits
Reorganize all commits on the current branch into clean, logical, atomic commits.
Instructions
Step 1: Analyze Current State
git branch --show-current
git log origin/main..HEAD --oneline
git diff origin/main...HEAD --stat
git status
Step 2: Preserve All Changes
- Stash uncommitted changes (if any):
git stash push -m "Pre-rearrange stash" - Soft reset all commits back to origin/main:
git reset --soft origin/main - Pop stashed changes (if any):
git stash pop
Step 3: Create Small, Logical Commits
Group changes by logical unit and commit in order:
- Schema/model/migration changes first
- Core logic/services second
- API/views/controllers third
- Tests fourth
- Configuration/misc last
Commit Message Format
type(scope): short description
Detailed explanation of WHAT, WHY, and HOW.
Types: feat, fix, refactor, test, docs, chore, perf
Check the project's commit format invariant or AGENTS.md for valid scopes. Do NOT invent new scopes: pre-push hooks may reject them.
Step 4: Verify
git log origin/main..HEAD --oneline
git diff origin/main...HEAD --stat
Ensure:
- All changes are committed (nothing left uncommitted)
- Each commit is atomic and self-contained
- Commits are in logical order
- The total diff matches what it was before reorganization
Cross-References
- Called by:
/develop-full(Phase 3) and/pr(commit organization step) - Before PR: Run
/reviewafter rearranging, then/pr
Rules
- Each commit = ONE logical change
- Earlier commits should not depend on later ones
- Keep commits small: easier to review and revert
- Never create standalone doc-count commits (e.g., "docs: update counts"): fold doc/count updates into the commit that introduced the change (the one that added the service, step, test, etc.)
- NEVER use emojis in any output
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.
- yesterday First seen · 89 lines · 25 tokens per session scan A b883150d4f1a
source-command-rearrange-commits is a skill published in the GitHub repository xsovad06/sova (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 25 tokens to every session and 551 once invoked, about $0.0001 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-09-05.
Other skills, from other repositories
github-commenting
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
commit-msg
You receive a git diff of staged changes via stdin. Generate a commit message.
requesting-code-review
Use when implementation is done and you need a structured pre-PR review workflow. Triggers: 'ready for review', 'review my changes before PR', 'pre-merge check', 'is this ready', 'submit for review'. NOT for: post-merge review (use code-review) or deciding how to integrate (use finishing-a-development-branch).
commit
Use when committing changes, staging files, saving work, or making a git commit. Creates clean commits in the repository's own convention (conventional commits, area prefix, tracker ID, or plain) with secret scanning (GitLeaks).
git
This skill should be used when the user asks to "commit changes", "create a pull request", "rebase safely", "manage branches", "fix merge conflicts", "undo a commit", "comment on a PR", "create a release", or performs any git/GitHub operations. Provides safety patterns, atomic commit formatting, PR descriptions…
comprehensive-review-pr-enhance
You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensure PRs follow best practices for clarity, size, and reviewability.