self-review

Answer "verify what you delivered, what did you gloss over, what did I miss?" about committed work since the last self-review, before /branch-review. The orchestrator resolves the range and hands off; a spawned worker tries to break it.

Guardrails

• Spawn a worker, mid tier stated explicitly (omitted inherits the parent's, not the balanced one; not cheapest/fastest either — judgment degrades there; never a vendor model name — this spec names the tier, you translate it to whatever your spawn tool calls its mid tier), and hand it this file's path — a worker has no skill text of its own. No delegation, no sub-spawning — every command the worker cites is one it ran itself.
• Ask and surface only. Never fixes anything. The user picks.

1. Orchestrator — resolve the range, then hand off

Dirty tree first: git status --porcelain prints any line → stop: the tree is dirty (list the paths), /self-review reviews commits not the working tree, commit then re-run. No worker spawned.

Hashes or a range given ($ARGUMENTS: one or more hashes, or <a>..<b>) → review exactly those commits, nothing else, on any branch: each hash via git show <sha>, a range via git log <a>..<b> and git diff <a>..<b>. Validate each hash, and both ends of a range, with git rev-parse --verify <x>^{commit}; reject anything starting with -. Hash/range mode never rewrites self-review-sha:.

Neither → on main/master, stop and ask for hashes or a range. Otherwise the bookmark is one line, self-review-sha:, in /branch-review's record (/self-review is its only writer):

grep '^self-review-sha:' .factory/remember/last-review.md || grep '^debrief-sha:' .factory/remember/last-review.md

No self-review-sha: line → the old debrief-sha: name, once (that is what the || does; the new name wins if both exist). Fails either check, starts with -, or the third exits 0 (an ancestor of main's merge-base is from an already-merged branch) → no bookmark:

git rev-parse --verify <sha>
git merge-base --is-ancestor <sha> HEAD
git merge-base --is-ancestor <sha> $(git merge-base main HEAD)

Valid (third command exits non-zero) → range <sha>..HEAD. No bookmark → whole branch, git merge-base main HEAD..HEAD. Range empty → "nothing new since the last self-review," stop, no worker spawned. Otherwise hand off — what was done, claims made (works / tested / done), files changed, the baseline suite totals if known, loose ends only you can know (a peer session not told, a silent open question, unshipped state) — and spawn one mid-tier worker.