deep-reviewlisted

# Deep Review — structured gap-detection before commit A structured 10-point review of your diff by an independent reviewer (fresh context, separate token budget). Catches the class of issues that automated tooling misses but humans find in PR review: - Completeness gaps (spec says X, code does Y) - Test/impl drift (test asserts old behaviour after code changed) - Dead code from partial refactors - Naming/behaviour mismatch - Doc-paraphrase drift - Cross-file consistency breaks ## When to use - Before committing a significant change - After a refactor — to catch leftover artifacts - When you want a second opinion on a diff - Before opening a PR — catch issues before reviewers do ## Step 1: Determine scope Check if the user specified a scope mode. Three modes are supported: | Mode | Trigger | Git command | |------|---------|-------------| | **staged** (default) | `--staged`, or no flag | `git diff --staged` | | **working** | `--working` | `git diff` | | **range** | `--range <ref>..<ref>` | `git diff <ref>..<ref>` | If the user didn't specify a mode, default to **staged**. If there are no staged changes in staged mode, check for unstaged changes and ask: ``` No staged changes found. There are unstaged changes in the working tree. Would you like to review those instead? ``` Use `AskUserQuestion`: - **Question:** `No staged changes. Review unstaged working tree changes instead?` - **Header:** `Scope` - **Options:** - `Yes, review working tree` — description: `Run git