Comprehensive MR 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:

   • tests - Review test coverage quality and completeness
   • code - General code review for project guidelines
   • all - Run all applicable reviews (default)

3. Identify Changed Files

   • Run git diff --name-only to see modified files
   • Check if MR already exists: glab mr view
   • Identify file types and what reviews apply

4. Determine Applicable Reviews

   Based on changes:

   • Always applicable: code-reviewer (general quality)
   • If test files changed: mr-test-analyzer

5. Launch Review Agents

   Sequential approach (one at a time):

   • Easier to understand and act on
   • Each report is complete before next
   • Good for interactive review

   Parallel approach (user can request):

   • Launch all agents simultaneously
   • Faster for comprehensive review
   • Results come back together

6. Aggregate Results

   After agents complete, summarize:

   • Critical Issues (must fix before merge)
   • Important Issues (should fix)
   • Suggestions (nice to have)
   • Positive Observations (what's good)
   • ALWAYS add relative file paths to the files

7. Provide Action Plan

   Organize findings:

   # MR Review Summary
   
   ## Critical Issues (X found)
   - [agent-name]: Issue description [file:line]
   
   ## Important Issues (X found)
   - [agent-name]: Issue description [file:line]
   
   ## Suggestions (X found)
   - [agent-name]: Suggestion [file:line]
   
   ## Strengths
   - What's well-done in this PR
   
   ## Recommended Action
   1. Fix critical issues first
   2. Address important issues
   3. Consider suggestions
   4. Re-run review after fixes