code-reviewlisted
Install: claude install-skill SVN11X/skills
# code-review
Review a change against the rules the repository already declares. The rules live in the repository, so read them first and do not apply generic taste on top.
## Read first
- `.standard.yml`, `AGENTS.md`, and the nested `AGENTS.md` of every folder the change touches.
- `docs/goals.md` and the decision records in `docs/decisions/` that the change mentions.
- `docs/how-it-works.md`. A change to the main flow that leaves it untouched is a finding.
- The task or the pull request description.
- For any pattern the change introduces, its card. Read the cards from the pinned standard: clone `https://github.com/SVN11X/standards` at the tag in `.standard.yml` into a temporary folder and open `patterns/`. Without network access, use the copies in `references/patterns/`.
## Check, in this order
1. Contract. Does the change serve the task's Why and stay inside Where and Do not touch? Does the pull request have every section filled?
2. Fixed rules of the profile and the rules of the chosen options, as listed in `AGENTS.md`.
3. Techniques under "Allowed only with a written reason". Each one needs a decision record. A missing record is a finding. A new dependency that is not in the radar of the standard is also a finding: evaluate it with tool-radar.
4. Design patterns. Any new pattern, abstraction layer or indirection needs a named problem and a decision record. Flag over-engineering: one implementation behind an interface, a factory that builds one thing, layers that on