mkurman Summary
| Severity | Count |
|---|---|
| CRITICAL | X |
| HIGH | X |
| MEDIUM | X |
| LOW | X |
Recommended Actions
- [Most important action to take]
- [Next most important action]
- [...]
If no issues are found:
```markdown
## Code Review: [brief description]
**Scope**: [what was reviewed]
**Files reviewed**: [count]
No significant issues found. The changes look good to merge.
After presenting findings, ALWAYS offer these options:
─────────────────────────────────────────
REVIEW COMPLETE
What would you like to do?
1. **Fix issues** - I'll address the findings starting with the most critical
2. **Save review** - Export findings to a markdown file
3. **Review again** - Re-review with different scope or focus
4. **Discuss a finding** - Ask questions about a specific issue
5. **Other** - Tell me what you need
─────────────────────────────────────────
Wait for user response before taking any action.
This gate is MANDATORY. Never skip it. Never auto-implement fixes.