deep-reviewlisted
Install: claude install-skill amit-mizrachi/claude-amit-mizrachi
# deep-review
One reviewer, reading deeply, instead of a squad of narrow ones. On this team's own commits it found every High the squad found plus two more, and 93% of what it reported was real (the squad: 46%). Benchmark and sources: `references/sources.md`.
## Step 1 - Pick what to review
- **Uncommitted work** (the usual case): snapshot it in a private index, so your index, files and branch are untouched and untracked files (respecting .gitignore) are included:
```bash
IDX=$(mktemp)
GIT_INDEX_FILE=$IDX git read-tree HEAD
GIT_INDEX_FILE=$IDX git add -A
HEAD_SHA=$(git commit-tree "$(GIT_INDEX_FILE=$IDX git write-tree)" -p HEAD -m "deep-review: working tree snapshot")
rm -f "$IDX"
```
The snapshot is an unreferenced commit nobody pushes. If the tree holds edits unrelated to this session, say so in the report.
- **A clean branch**: `HEAD_SHA=$(git rev-parse HEAD)`.
- **Base** in both cases: `BASE_SHA=$(git merge-base origin/<default branch> "$HEAD_SHA")` (fetch first).
- **A PR handed over by review-pr**, or a PR the user names: exactly its base and head.
- No diff between base and head: say so and stop.
## Step 2 - Gather the intent, verbatim
Collect what the change is supposed to do: the Monday ticket text, the PR description, or the plan the session followed. Quote it; never write your own summary of the requirements, because a summary written by someone who already knows the problems steers the reviewer toward them. If there is none, pass "none given".