// Review current code changes by dispatching parallel specialized review agents (Vue, TypeScript, a11y, performance, security, tests). Use proactively before committing or opening a PR, or when the user asks to "review", "check", "audit", or "look over" their changes.
| name | check |
| description | Review current code changes by dispatching parallel specialized review agents (Vue, TypeScript, a11y, performance, security, tests). Use proactively before committing or opening a PR, or when the user asks to "review", "check", "audit", or "look over" their changes. |
| allowed-tools | Bash(git diff:*), Bash(git status), Bash(git branch:*), Bash(git merge-base:*), Task |
Review current changes using specialized review agents.
<git_status>
!git status
</git_status>
<current_branch>
!git branch --show-current
</current_branch>
<merge_base>
!git merge-base main HEAD 2>/dev/null || echo ""
</merge_base>
<branch_changed_files>
!git diff --name-only main...HEAD 2>/dev/null || echo ""
</branch_changed_files>
<branch_diff>
!git diff main...HEAD 2>/dev/null || echo ""
</branch_diff>
<uncommitted_changed_files>
!git diff --name-only HEAD
</uncommitted_changed_files>
<staged_diff>
!git diff --cached
</staged_diff>
<unstaged_diff>
!git diff
</unstaged_diff>
Determine review mode:
<staged_diff> or <unstaged_diff> have content<branch_diff>Based on changed files and diff content, select 2-4 reviewers:
| Reviewer | Select When |
|---|---|
| vue-reviewer | Any .vue files |
| typescript-reviewer | Complex types, generics, type assertions |
| kcd-test-reviewer | Any .spec.ts or .test.ts files |
| accessibility-reviewer | UI elements: buttons, inputs, modals, forms |
| performance-reviewer | Reactivity patterns, computed/watch, large lists |
| architecture-reviewer | Cross-feature imports, new feature files |
| security-reviewer | User input handling, v-html, external data |
| vueuse-reviewer | Manual event listeners, localStorage, timers |
| fowler-refactoring-reviewer | Large functions, code duplication |
Launch 2-4 Task tools in a single message with all selected reviewers at once. Each reviewer prompt should include the changed files list and the relevant diff.
After all reviewers complete, compile findings into:
# Code Review Report
## Summary
[2-3 sentences]
## Critical Issues
[Must fix - or "None"]
## [Reviewer Name]
[Findings or "No issues"]
## Recommended Actions
1. [Priority actions]
Inspect GitHub Actions / CI status for the current branch and plan fixes when checks fail. Use proactively after pushing, or when the user mentions "CI", "pipeline", "GitHub Actions", "failing checks", "build failing", or asks "why is CI red".
Run ESLint across the project and fix reported errors and warnings. Use when the user asks to "lint", "fix lint errors", "run eslint", or before committing/shipping to ensure a clean lint pass.
Squash-merge the current PR into main, delete the branch, pull latest, and start a new feature branch. Use when the user says "merge this PR", "merge and start new branch", or is done with a PR and ready to start the next task.
Generate or update a structured pull request with summary, user impact, acceptance criteria, QA scope, risk areas, and executable test scenarios, then open it with GitHub CLI.
Deep research on a technical problem using parallel subagents for web docs, Stack Overflow, and codebase exploration, saving a markdown report to docs/research/. Use when the user says "research X", "investigate X", "find out how X works", or needs evidence-based recommendations before implementing.
Fetch CodeRabbit review comments on the current PR, validate each against project conventions, implement valid fixes, and reply to resolve each conversation. Use proactively when CodeRabbit leaves review comments, or when the user says "review coderabbit", "address coderabbit feedback", or "fix coderabbit comments".