Skip to content

Code Review

code-review owns:

Does this implementation introduce a meaningful correctness or maintainability risk?

  • reviewing a diff or pull request
  • validating a risky refactor
  • checking whether implementation matches the intended contract
  • checking whether verification is faithful and sufficient

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 findings

Prefer concrete, reproducible findings over stylistic preference.

Use $code-review on this diff.
Prioritize correctness blockers and missing faithful verification.

Read the complete code-review instructions.