Review local branches, pull requests, commits, or files and address issues. The skill selects a single-agent or multi-agent workflow based on the environment, with automatic fixes for lower-risk issues and confirmation for high-risk changes.
Automated code review and fix for local branches, PRs, commits, and files. Supports single-agent interactive fix and multi-agent adversarial review with auto-fix.
Review the instructions the agent will receive before you install.
Automated code review for local branches, PRs, commits, and files. Detects review mode from arguments and routes to the appropriate review flow — either single-agent review on protected branches or when teams are unavailable, or multi-agent deep review with risk-based auto-fix.
All user-facing text matches the user's language. Start the review immediately based on the routing rules below — do NOT ask the user to choose the review mode upfront. Interactive prompts inside each flow (e.g. final confirmation of high-risk fixes) still use your interactive dialog tool (e.g. AskUserQuestion).
Run pre-checks, then match the first applicable rule top-to-bottom:
git branch --show-current → record whether on main/master.git status --porcelain → record whether uncommitted changes exist.| # | Condition | Action |
|---|---|---|
| 1 | $ARGUMENTS is diag | → references/diagnosis.md |
| 2 | $ARGUMENTS is a PR number or URL containing /pull/ | → references/pr-review.md |
| 3 | On main/master branch | → references/local-review.md |
| 4 | Agent teams NOT supported | → references/local-review.md |
| 5 | Everything else | → references/teams-review.md with FIX_MODE=low_medium |
Each → means: Read the target file and follow it as the sole remaining
instruction. Ignore all sections below. Do NOT review from memory or habit —
each target file defines specific constraints on how to obtain diffs, apply
fixes, and submit results.
Pass $ARGUMENTS to the target file. For teams-review, also pass FIX_MODE
(fixed to low_medium: multi-agent review auto-fixes low and medium risk
issues; high-risk issues such as API changes or architecture impact are
deferred to user confirmation).
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Accept screenshot baseline changes by running the project's dedicated script, then commit the updated version.json using the project's commit conventions. This provides an explicit command for recording changes to the screenshot comparison baseline.
Commit local changes to the current Git branch with a message based on the project's conventions. When staged and unstaged changes coexist, choose which to include. The skill does not push changes or create pull requests.
Create PAGX vector graphics files from a visual description, HTML file, or public URL, including supported animations. Edit existing designs, check their appearance, and export them to SVG, HTML, or PPTX.
Commit and push local changes, then create a pull request or update an existing one based on the branch state. The skill prepares commit messages and new pull request details from the changes being submitted.
Review a branch's commits, combine adjacent changes that belong together, and improve commit messages. A rebuilt history is prepared separately and replaces the original branch only after the user reviews and confirms the proposed changes.