Skill v1.0.0

version: "1.0.0" name: review description: Review code changes for security, performance, bugs, and quality. Reviews staged changes, unstaged changes, specific commits, or PR-ready diffs.

tags: [gsd-2, skills, review, security, performance]

Summary

Recommended Actions

1. [Most important action to take]
2. [Next most important action]
3. [...]

 
If no issues are found:
 

Code Review: [brief description]

Scope: [what was reviewed] Files reviewed: [count]

No significant issues found. The changes look good to merge.

 
</output_format>
 
<decision_gate>
 
**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.
 
</decision_gate>