eooo-io Code Review
Purpose
Review a code change and produce actionable feedback. The output is concrete enough that the author can fix issues without a follow-up conversation.
Review dimensions
- Correctness
- Readability
- Complexity
- Security
- Performance
- Test quality
- Architecture fit
- Operational risk
Output format
## Summary
## Critical issues
## Suggested improvements
## Tests to add or update
## Questions or assumptions
Rules
- Be specific. "Unclear" is not feedback; quote the line and explain why.
- Explain why each issue matters; consequences anchor priority.
- Prefer fix suggestions or small diffs when the change is mechanical.
- Do not invent project requirements.
- Mark uncertainty clearly. Reviewing is not bluffing.