review

Identify defects, risks, and regressions in proposed code changes before approval.

2|Updated Dec 31, 2025
One-click install
npx skills add https://github.com/leanbusqts/agent47 --skill review-leanbusqts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/leanbusqts/agent47/tree/main/templates/skills/review
Command: npx skills add https://github.com/leanbusqts/agent47 --skill review-leanbusqts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams catch defects, risks, and regressions in proposed changes before they are merged, reducing post-release incidents and rework.

Core Features & Use Cases

  • Structured feedback: Restate changes and verify alignment with acceptance criteria.
  • Risk detection: Identify regressions, edge cases, and impact on related components.
  • Actionable outputs: Deliver prioritized issues, severity, and concrete recommendations.

Quick Start

Use the review skill on a diff or pull request by providing the patch or changed files and the acceptance criteria. For example, review the changes in PR #123 against the project requirements and tests to receive a concise issues list and recommended fixes.

Frequently Asked Questions about review

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

FAQPage Schema
How do I find defects and regressions in a pull request before merging?

To find defects and regressions in a pull request before merging, provide the diff, changed files, and acceptance criteria to receive structured feedback, context checks, and actionable recommendations.

What is the best way to verify code quality in a diff against project requirements?

The best way to verify code quality in a diff against project requirements is to apply structured reviews that restate changes, validate coverage, and assess risks to ensure alignment with tests.

How do I perform a structured code review on changed files?

You perform a structured code review on changed files by submitting the patch along with project requirements, which triggers risk detection, edge case identification, and prioritized issue reporting.

Can I use code review to detect risks in modified tests and requirements?

Yes, you can use code review to detect risks in modified tests and requirements, as the process explicitly evaluates changed files across code, tests, and requirements for potential regressions.

How do I get actionable recommendations for issues found in my code diff?

To get actionable recommendations for issues found in your code diff, run a review that outputs prioritized issues with severity levels and concrete fixes to reduce post-release incidents.