Review Checklist

Must

• Behavior matches acceptance criteria.
• No obvious edge cases missing.
• Tests cover new behavior.
• No secrets or dangerous commands.

Should

• Small, cohesive modules.
• Names are clear.
• Errors handled at boundaries.