Review and Fix

Review code changes as a senior engineer would: investigate context first, weigh trade-offs against the change type, then organize findings for user action.

When to Use

• The user asks to review their changes, the git diff, or a commit range ("review my changes", "check the diff", "code review")
• The user wants issues found and fixed before committing ("review and fix", "fix the issues")
• The user invokes /review-and-fix

When NOT to Use

• Full codebase auditing (use a broader code review tool)
• Security auditing specifically (use a dedicated security skill)
• Performance profiling (different domain)
• Generating tests (separate workflow)

Inputs