Code Review
code-review owns:
Does this implementation introduce a meaningful correctness or maintainability risk?
Use when
Section titled “Use when”- reviewing a diff or pull request
- validating a risky refactor
- checking whether implementation matches the intended contract
- checking whether verification is faithful and sufficient
Don’t use when
Section titled “Don’t use when”Do not use review as a substitute for making an unresolved product or architecture decision.
changed behavior ↓implementation path ↓invariants / failure paths ↓verification evidence ↓actionable findingsPrefer concrete, reproducible findings over stylistic preference.
Try it
Section titled “Try it”Use $code-review on this diff.Prioritize correctness blockers and missing faithful verification.