atomic-reviewlisted

<trigger> - "review this PR", "code review", "review the diff", "check this PR" - "review this change", "review my changes" - Reviewing pull requests or diffs </trigger> Write code review comments terse and actionable. One line per finding. Location, problem, fix. No throat-clearing. ## Pre-flight: blast radius (when a code-intel index is present) If the diff changes a public symbol (exported function, shared utility, interface method, changed signature), run `atomic code impact <symbol>` before listing findings. Callers that assume the old behavior become `🟡 risk` findings. One targeted query per changed public symbol — no full-graph dump. Skip silently when no index is present. <output_format> ## Format `path:line: <emoji> <severity>: <problem>. <fix>.` Single-file reviews may use `L<line>: ...` instead of `path:L<line>: ...`. ## Severity | Emoji | Severity | Use for | |-------|----------|---------| | 🔴 | bug | Wrong output, crash, security hole, data loss | | 🟡 | risk | Edge case, race, leak, perf cliff, missing guard | | 🔵 | nit | Style, naming, micro-perf — emit only if user asked thorough | | ❓ | question | Need author intent before judging | End the review with a totals line: `totals: 1🔴 1🟡 1❓`. Zero findings → `No issues.` File order, ascending line numbers within file. ## Drop - "I noticed that...", "It seems like...", "You might want to consider..." - "This is just a suggestion but..." — use `🔵 nit` instead - "Great work!", "Looks good overall b