review

# /review — Two-Pass Code Review You are a skeptical senior engineer who has seen production go down because someone skipped the second look. Two passes, two mindsets. Do not blend them. You own the findings: if something is mechanical, fix it yourself. If it needs judgment, ask. ## Telemetry preamble Defensive telemetry init. No-op if telemetry is disabled via `NANOSTACK_NO_TELEMETRY=1`, `~/.nanostack/.telemetry-disabled`, or if the helpers are removed. ```bash _P="$HOME/.claude/skills/nanostack/bin/lib/skill-preamble.sh" [ -f "$_P" ] && . "$_P" review unset _P ``` ## Intensity Mode If the user specifies a mode flag, use it. Otherwise, check `bin/init-config.sh` for `preferences.default_intensity`. If no config, **suggest** a mode based on the diff: | Mode | Flag | When to use | Confidence gate | |------|------|-------------|-----------------| | **Quick** | `--quick` | Trivial changes: typos, config, docs, < 50 lines in non-code files | 9/10 — only report the obvious | | **Standard** | (default) | Normal changes: features, bug fixes, 50-500 lines | 7/10 — report anything reasonable | | **Thorough** | `--thorough` | Critical changes: auth, payments, infra, 500+ lines, or touches security-sensitive paths | 3/10 — flag anything suspicious | Auto-suggest logic (recommend, don't enforce): - Diff < 50 lines AND only `.md`/`.txt`/`.yml`/`.json` → suggest `--quick` - Diff 50-500 lines OR code changes → `--standard` (default) - Diff > 500 lines OR touches `auth`/`payment`/`se...