code-review

Evaluate pull request diffs against a checklist and generate severity-classified review documents.

31|8|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/itallstartedwithaidea/agent-skills --skill code-review-itallstartedwithaidea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/itallstartedwithaidea/agent-skills/tree/main/skills/software-dev/code-review
Command: npx skills add https://github.com/itallstartedwithaidea/agent-skills --skill code-review-itallstartedwithaidea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code Review reduces the risk of merging faulty, insecure, or poorly maintained changes by applying a structured quality gate before code reaches production.

Core Features & Use Cases

  • Pre-merge checklist validation: Runs mechanical checks first (tests, linter, type checking, uncommitted/unwanted secrets, and documentation freshness) to catch issues early.
  • Severity-classified findings: Produces standardized results split into Critical, High, Medium, and Low so teams can respond appropriately.
  • Actionable resolution tracking: Requires concrete suggested fixes per finding and drives merge decisions (request changes vs approve with reservations vs approve).

Quick Start

Use the code-review skill when you want an AI to review a pull request diff against a pre-merge checklist and return a severity-based review document with suggested fixes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate a pre-merge code review for a pull request diff?

Automated code review evaluates pull request diffs against a structured pre-merge checklist to validate correctness, security, and performance. It generates a standardized review document containing severity-classified findings and actionable suggested fixes.

What is severity classification in code review findings?

Severity classification in code review splits standardized findings into Critical, High, Medium, and Low categories. This allows development teams to respond appropriately to vulnerabilities and drives clear merge decisions based on issue criticality.

How do I enforce a quality gate before merging code changes?

Enforcing a pre-merge quality gate requires running mechanical checks on tests, linters, type checking, and unwanted secrets before code reaches production. The review process validates documentation freshness and produces actionable, file-and-line-scoped findings.

Can I use an automated checklist to catch security issues in a pull request?

Yes, a security review applies mechanical checks to catch uncommitted or unwanted secrets within the pull request diff. It evaluates changes against a pre-merge checklist to identify security vulnerabilities and classify them by severity.

Does code review provide actionable suggested fixes for identified issues?

Code review requires concrete suggested fixes per identified finding and scopes them to specific file and line numbers. This actionable resolution tracking drives final merge recommendations like request changes or approve with reservations.