code-review

Coordinates parallel accessibility, code quality, and performance reviewers over a git diff into one merged report.

Updated May 26, 2026
One-click install
npx skills add https://github.com/robot-denny/ai-sketchlab --skill code-review-robot-denny
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/robot-denny/ai-sketchlab/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/robot-denny/ai-sketchlab --skill code-review-robot-denny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a change across accessibility, code quality, and performance dimensions manually is slow and easy to under-scope, especially when work was committed across several steps. This Skill dispatches the project's registered reviewers in parallel over the correct diff scope and merges their findings into one de-duplicated, severity-ranked report with an action plan. ## Core Features & Use Cases - Parallel multi-role review: Discovers registered reviewers (accessibility, code quality, performance) by name and description, preferring project-tailored reviewers over canonical ones, and runs them concurrently over the same diff. - Correct diff scoping: Defaults to uncommitted changes, or resolves the full branch versus its upstream merge-base when the increment spans multiple commits, including untracked files read in full. - Merged actionable report: De-duplicates overlapping findings, keeps every unique finding, ranks by Blocker/Major/Minor/Nit, and produces an ordered action plan that is only applied after explicit approval. - Use Case: After implementing a feature across several commits, run the review before pushing to get a single consolidated report covering WCAG issues, code quality problems, and performance regressions, then approve the fix plan. ## Quick Start Ask the assistant to run the code-review skill on the current branch before committing.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a git branch before merging?

Run the code-review skill with the branch scope. It resolves the upstream tracking branch, computes the merge-base, diffs committed and uncommitted changes, reads untracked files in full, and dispatches accessibility, quality, and performance reviewers in parallel.

How do I run accessibility, performance, and code quality reviews together?

The skill discovers registered reviewer agents by name and description, then invokes all of them in parallel over the same diff. Findings are merged into one report ranked by Blocker, Major, Minor, and Nit severity with a combined action plan.

What happens if a reviewer agent is not installed?

If a role has no registered reviewer, that pass runs inline under the same severity scale and merge rules rather than being skipped. The report always states which roles were dispatched and which ran inline, so a thin review is never mistaken for a clean one.

Does the code review apply fixes automatically?

No. The skill produces a merged report and an ordered action plan, then asks for explicit approval before changing any code. It never edits files or makes formatting-only changes unless they fix a cited issue.

Why does a review miss changes committed in earlier steps?

The default uncommitted scope only sees working-tree changes, so work committed across multiple steps is invisible. Use the branch scope, which diffs everything from the upstream merge-base plus uncommitted and untracked files.