code/commands/builtins/review.md

---
name: review
description: Review the current changes for bugs and quality issues
argument-hint: Optional file or PR to review
---
## Review Task

Review the current code changes for quality and correctness.

If $ARGUMENTS is provided, review that specific file or changeset.
Otherwise, review the current `git diff HEAD`.

## Process

1. Use `bash` to get the diff:
   - If arguments given and it's a file: `git diff HEAD -- $ARGUMENTS`
   - Otherwise: `git diff HEAD`

2. Read each changed file fully with `read_file` for context.

3. Apply the code-review skill — focus on HIGH SIGNAL issues only:
   - Bugs that will cause incorrect behavior
   - Security issues (hardcoded secrets, injection, path traversal)
   - Syntax/type errors
   - Clear convention violations

4. Do NOT flag:
   - Subjective style preferences
   - Potential issues that depend on specific inputs
   - Pedantic nitpicks

5. Output your review in this format:

```
## Code Review

### Critical
- `file:line` — Description and fix

### High
- `file:line` — Description and fix

### Medium
- `file:line` — Description and fix

### Summary
Brief overall assessment.
```

If no issues: state "No issues found. Checked for bugs, security, and conventions."