deep-review

# Deep Review — Parallel Competency-Based Code Review Inspired by Memento workflow engine's parallel review pattern. Philosophy: one focused expert per domain > one generalist checking everything. --- ## Step 0: Determine scope ```bash BASE=$(gh pr view --json baseRefName -q .baseRefName 2>/dev/null || git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@refs/remotes/origin/@@' || echo "main") echo "BASE: $BASE" git fetch origin "$BASE" --quiet 2>/dev/null || true echo "=== DIFF STATS ===" git diff "origin/$BASE" --stat echo "=== CHANGED FILES ===" git diff "origin/$BASE" --name-only echo "=== DIFF SIZE ===" git diff "origin/$BASE" --shortstat ``` Store the BASE branch name and list of changed files. You'll need them in every subsequent step. If there is no diff, stop: "Nothing to review — no changes against $BASE." --- ## Step 1: Scoping — select relevant competencies Based on the changed files, select ONLY the competencies that are relevant. Do NOT run all 8 for a 3-file CSS change. ### Competency selection rules | Competency | Trigger files/patterns | |---|---| | **security** | auth, middleware, routes handling user input, env files, CORS, JWT, crypto, passwords, tokens, API keys | | **performance** | database queries, loops over collections, API endpoints, bundle config, image/asset handling, caching | | **architecture** | new files/modules, cross-module imports, service boundaries, DI patterns, >5 files changed | | **database** | migrations, schema c...