Code Review
Review code changes, diffs, and modified files for quality and correctness.
When to Use
Activate when users ask to:
- •Review code changes or diffs
- •Check code quality
- •Analyze uncommitted work
- •Review changes since diverging from a branch
Workflow
- •
Identify Changes
- •Use
git_diffto get the current diff - •Identify files that have been modified
- •Use
- •
Analyze Each File
- •Read the full file context with
read_file - •Understand the purpose of changes
- •Check for potential issues
- •Read the full file context with
- •
Provide Feedback
- •Note any bugs or logic errors
- •Suggest improvements
- •Highlight security concerns
- •Comment on code style and conventions
Review Criteria
- •Correctness: Does the code do what it's supposed to?
- •Security: Are there any vulnerabilities?
- •Performance: Are there obvious inefficiencies?
- •Maintainability: Is the code readable and well-structured?
- •Testing: Are changes adequately tested?
Response Format
Provide structured feedback:
- •Summary of changes
- •Specific issues found (if any)
- •Suggestions for improvement
- •Overall assessment