sova: Command for Claude Code

Full Review Pipeline

Run a complete pre-push quality pipeline: simplify code, review for issues, then organize commits into clean history.

Scope: $ARGUMENTS

Phase 1: Simplify

Follow the /simplify workflow. Review all changed code for opportunities to reduce complexity:

1. Get the diff scope:

   BASE=$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's#^origin/##')
   BASE=${BASE:-main}
   git fetch --quiet origin "$BASE"
   git diff "origin/$BASE"...HEAD --stat
   git diff --cached --stat
   git diff --stat
   

2. For each changed file, read the entire file and check:

   • Code reuse: does new code duplicate existing utilities or helpers? Search the codebase.
   • Over-engineering: unnecessary abstractions, premature generalization, excessive configurability
   • Dead code: unused imports, unreachable branches, commented-out code
   • Redundancy: repeated logic that could be a shared helper (only if 3+ occurrences)
   • Complexity: can any function be simplified without losing clarity?
   • Efficiency: redundant computations, repeated file reads, duplicate API calls

3. Apply simplifications directly. After each change, verify tests still pass (see CLAUDE.md for commands).

4. If no simplifications are needed, state that and move on.

Phase 2: Review

Follow the /review command workflow:

1. Review all changed files for bugs, security, performance, test coverage, consistency, doc freshness, and scout rule (fix pre-existing issues in touched files).
2. Score each finding (1-10 priority). Address all findings (fix or acknowledge with justification).
3. Run the full CI-equivalent checks: make check. Fix any failures before proceeding.
4. Report findings in the standard review format.

See /review for the full review checklist and scoring criteria.

Phase 3: Organize Commits

Follow the /rearrange-commits command workflow:

1. Snapshot uncommitted work as a WIP commit and create a backup branch, then soft reset to the fork point (git merge-base HEAD "origin/$BASE"), exactly as /rearrange-commits Step 2 does. Never reset to origin/$BASE itself: re-committing this branch's tree on top of a base that moved silently reverts everything the base gained. Never use git stash: the stash stack is shared by every worktree and session.
2. Create small, logical, atomic commits in dependency order.
3. Verify: all changes committed, each commit atomic, total diff matches the backup branch.