pre-reviewlisted

## What This Does Prepares the full context payload that `superpowers:requesting-code-review` needs to perform a high-quality code review. This skill owns the **gather** phase; Superpowers owns the **review** phase. **Delegation chain:** ``` /pre-review → gather context → package → superpowers:requesting-code-review → code-reviewer agent ``` ### Gather phase (this skill): 1. `git diff --stat HEAD` — changed files with line counts 2. `git diff HEAD` — full diff (compressed via safe-exec if >5 KB) 3. Manifest freshness check: `ls -la <IDE_DIR>/shadow/**/_manifest.lightweight.yaml` 4. Impact radius analysis (see below) 5. Set review marker. It MUST hash the **repo root**, not `$PWD` — `pre-commit-review.sh` normalizes via `git rev-parse --show-toplevel`, so a marker keyed to a subdirectory will not match (and `md5sum` alone does not exist on stock macOS; `echo` would add a newline): `touch /tmp/.claude-review-done-$(printf "%s" "$(git rev-parse --show-toplevel):$(whoami)" | (md5 -q 2>/dev/null || md5sum | awk '{print $1}') | cut -c1-8)` ### Impact radius analysis: - **If code-review-graph MCP is available:** call `detect_changes_tool` with changed file list, then `get_impact_radius_tool` to get importers and downstream consumers. - **If MCP not available:** use `rg`-based heuristic — for each changed file, count importers: `rg -l "import.*from.*<filename>" --type ts | wc -l` ## When to Use **Trigger:** Before any `git commit` or MR creation. Invoked manually v