# code-review evals — how to run

These cases are routing + capability checks for the `code-review` skill; there is no automated runner. Run them manually or via an orchestrator. For routing, read each `should_trigger` prompt and confirm the skill's description would fire on it (especially the spec-less diff/PR cases and the non-obvious dependency-bump one), then read each `should_not_trigger` prompt and confirm the description routes it to the named sibling — the load-bearing boundary is `review` vs `code-review` (review needs `02-DOCS/wiki/sdd/` and owns the receiving loop; code-review needs only the diff). For capability, hand an agent the scenario diff and score the response against the rubric: the planted-non-bug line is the real test — a review that flags the guarded-upstream SQL call as a blocker fails on signal-to-noise even if it caught the real bug. Also confirm it stayed read-only since no `--comment`/`--fix` was passed.
