Mackewinsson Code Review
Focus order
- Correctness — logic, edge cases, regressions
- Security — injection, auth, secrets, unsafe defaults
- Scope — unrelated changes, over-engineering
- Conventions — match surrounding code and project patterns
- Tests — meaningful coverage for changed behavior
Shared / risky files
Before approving edits to shared utilities, hooks, or contexts:
- List what else depends on them
- Flag blast radius to the user
Feedback format
- Critical — must fix before merge
- Suggestion — worth improving
- Nice to have — optional
Use code citations: ```startLine:endLine:path for references.
Output structure
## Summary
One paragraph.
## Critical
- ...
## Suggestions
- ...
## Test gaps
- ...
Keep review proportional to change size.