code-review

Review code changes and categorize issues with merge verdicts.

10|1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/andresdiegolanda/design-first-ai --skill code-review-andresdiegolanda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/andresdiegolanda/design-first-ai/tree/main/context/skills/code-review
Command: npx skills add https://github.com/andresdiegolanda/design-first-ai --skill code-review-andresdiegolanda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a consistent, team-specific quality gate during pre-merge reviews so that architectural regressions, unhandled error paths, and deviations from agreed designs are caught before code lands.

Core Features & Use Cases

  • Categorised findings: Produces Breaking (block merge), Important (must address), and Suggestions (optional) classifications for each observation.
  • Implementation guide checks: Compares changes against the project's implementation guide and flags deviations as findings.
  • Actionable references: Each finding references specific files, classes, methods, or lines and ends with a clear verdict: merge, merge with changes, or do not merge.
  • Use Case: Use when reviewing a completed feature branch or pull request to ensure senior-level architectural judgment is consistently applied.

Quick Start

Review the provided diff or pull request using the code-review skill and return Breaking, Important, and Suggestions sections with file/line references and a final merge verdict.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I run a code review before merging a pull request?

To run a code review before merging, provide the pull request diff, file sets, or pasted code. The skill applies a quality gate to identify blocking, important, and suggestion-level issues, returning a clear merge verdict.

How does a pre-merge quality gate check for implementation guide deviations?

A pre-merge quality gate checks for implementation guide deviations by comparing code changes against the project's agreed designs. It flags architectural regressions and unhandled error paths as categorized findings before code lands.

What is the best way to categorize pull request review findings?

The best way to categorize pull request review findings is by severity: Breaking issues block the merge, Important issues must be addressed, and Suggestions are optional. Each finding should reference specific files or lines.

Can I use a review checklist to enforce a merge verdict on pasted code?

Yes, you can use a review checklist to enforce a merge verdict on pasted code. The review process evaluates completed work and concludes with a clear verdict: merge, merge with changes, or do not merge.

When do I need an automated code review for a feature branch?

You need an automated code review for a feature branch when you want to ensure senior-level architectural judgment is consistently applied. It catches unhandled error paths and architectural regressions before code lands in the main branch.