code-review

# Code Review ## Planner Entry Run this local review only when the user explicitly asks or an actionable PR/CI finding requires it. Do not use it automatically before opening a PR: the two configured PR AI reviewers are the semantic-review gate. Review the current changes in the codebase (Go backend + Vite/React SPA monorepo). Every finding needs a `file_path:line_number` reference, an explanation of *why* it matters, and a concrete fix. Start from intent and evidence: read the spec/task first when available, then changed tests before production code. Tests reveal the expected behavior and whether the change is actually verified. ## Available skills - **`/tdd`** — Recommend when flagging untested logic. The author can use this to add tests. ## Steps ### 1. Identify changed files and check scope Determine the right diff scope: - **Local changes**: `git diff --name-only` (unstaged) and `git diff --cached --name-only` (staged) - **PR review**: `git diff origin/<base_branch>...HEAD --name-only` to diff against the base branch For an existing PR, first confirm the exact head under review. Do not assume the local checkout is current: inspect the PR's base branch and head SHA, fetch the head if needed, and use that immutable SHA in the diff. If the current PR head cannot be fetched, say so rather than reporting a stale checkout as a review of the current PR. Record the base and head SHA for each review round. A new contributor push starts a new round: reassess prior findi...