review-pull-requests

# Comprehensive PR Review

Run a comprehensive pull request review using multiple specialized agents, each focusing on a different aspect of code quality.

**Review Aspects (optional):** "$ARGUMENTS"

## Review Workflow:

1. **Determine Review Scope**
   - Check git status to identify changed files
   - Parse arguments to see if user requested specific review aspects
   - Default: Run all applicable reviews

2. **Available Review Aspects:**

   - **comments** - Analyze code comment accuracy and maintainability
   - **tests** - Review test coverage quality and completeness
   - **errors** - Check error handling for silent failures
   - **types** - Analyze type design and invariants (if new types added)
   - **code** - General code review for project guidelines
   - **simplify** - Simplify code for clarity and maintainability
   - **all** - Run all applicable reviews (default)

3. **Identify Changed Files**
   - Run `git diff --name-only` to see modified files
   - Check if PR already exists: `gh pr view`
   - Identify file types and what reviews apply

   **Error handling:**
   - If `git diff` fails (not a git repo): Report error clearly and stop
   - If `gh pr view` fails with "no PR found": Expected for pre-PR reviews, continue with git diff
   - If `gh pr view` fails with auth error: Note that GitHub CLI authentication is needed
   - If no changed files found: Report "No changes detected" and stop

4. **Determine Applicable Reviews**

   Based on changes:
   - **Always applicable**: kata-code-reviewer (general quality)
   - **If test files changed**: kata-pr-test-analyzer
   - **If comments/docs added**: kata-comment-analyzer
   - **If error handling changed**: kata-failure-finder
   - **If types added/modified**: kata-type-design-analyzer
   - **After passing review**: kata-code-simplifier (polish and refine)

5. **Launch Review Agents**

   **Sequential approach** (one at a time):
   - Easier to understand and act on
   - Each report is complete before next
   -