code-review

When running a code review, follow the process outlined here. ## Project Context - git installed: !`which git 2>/dev/null || echo "not installed"` - CLAUDE.md: !`find . -maxdepth 1 -name "CLAUDE.md" -type f` - project-discovery.md: !`find . -maxdepth 3 -name "project-discovery.md" -type f` - personal config directory: !`bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude"` - project .han/config.md: !`cat .han/config.md 2>/dev/null || echo ""` As your first action, use the Read tool on `.han/config.md` inside the `personal config directory` path above. A read that returns no file is no personal configuration: continue silently. When that file or the `project .han/config.md` probe supplies content, apply it per [config-rule.md](../../references/config-rule.md), which governs precedence between the two files, relative-path resolution, and what to do with a file that reads but cannot be used. ## Review Constraints Severity levels: - **Critical** — Must fix before merge. Security vulnerabilities, data corruption risk, breaking API changes, data isolation failures. - **Warning** — Should fix. Bugs that don't corrupt data, significant performance issues, missing required tests, missing error handling. - **Suggestion** — Consider improving. Style improvements, optional performance gains, documentation gaps, refactoring opportunities. Severity calibration is governed by **Step 3.3** (the authoritative home for size-based demotion). Ma...