checklisted

A gut-check between edits: run the gates, then fan the specialist reviewers over **uncommitted changes only**. Read-only — no edits, no commit, no push. Use it mid-feature after a meaningful chunk of work, and before `/gitpush` as a safety net. It is not a branch review: committed history is out of scope. ## Phase 0 — Scope and gates ```bash git status --porcelain git diff --name-only git diff --staged --name-only ``` Empty on all three → say there is nothing uncommitted and stop. Then run the gates, because a review of code that does not compile is wasted: ```bash bun run lint bun run test ``` Report a failure immediately and stop — a red gate is the finding. ## Phase 1 — Fan out Split the changed files and dispatch **in one message so they run in parallel**: | Changed | Reviewer | | ------------------------------- | ------------------------------ | | anything under `src/**` | `extension-security-reviewer` | | anything under `webview/src/**` | `webview-design-reviewer` | | either | a correctness pass — see below | Give each agent the explicit file list and this instruction: _review only these files, against the working-tree diff, and report HIGH/CRITICAL first._ The correctness pass is a general-purpose agent asked to find bugs a reader would miss: wrong condition, off-by-one, a promise not awaited, an error path that swallows, state that can go stale. Tell it to ignore style — t