reviewlisted

# Code Review Reviews against the full Darkroom quality checklist defined in the reviewer agent. Focus areas: TypeScript strictness, React patterns, accessibility, performance, security, file structure. ## Current State - Branch: !`git branch --show-current 2>/dev/null || echo "unknown"` - Staged files: !`git diff --staged --stat 2>/dev/null || echo "nothing staged"` - Unstaged files: !`git diff --stat 2>/dev/null || echo "nothing unstaged"` ## Get Changes ```bash # Unstaged changes git diff # Staged changes git diff --staged # Specific file git diff path/to/file ``` ## Output Format ``` ## Summary [1-2 plain-English sentences: what this change does, then your overall read] ## Critical Issues - [Must fix before merge] ## Warnings - [Should fix, but not blocking] ## Suggestions - [Nice to have improvements] ## Verdict [APPROVED / NEEDS CHANGES / BLOCKED] ``` ## Remember - Be constructive, not just critical - Explain WHY something is an issue - Comments in plain English — explain the issue and its impact like you're talking to a teammate, not citing a rulebook. No jargon dump. - Suggest specific fixes - If you find a pattern worth remembering, save it via auto-memory (personal) or `/share-learning` (team-wide). --- ## Variant: Summarize Inbound PR Comments When the user asks "what did reviewers say" or wants a digest of feedback on the active PR (not a self-review of local diff): 1. Resolve the active PR for the current branch. 2. Fetch review comments (file/