review

Review pull request diffs for correctness, quality, and security.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/fyodoriv/agentbrew --skill review-fyodoriv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/fyodoriv/agentbrew/tree/main/skill-plugins/dev/review
Command: npx skills add https://github.com/fyodoriv/agentbrew --skill review-fyodoriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews are time-consuming and inconsistent. This skill provides a structured approach to evaluate code changes for correctness, domain logic, quality, testing, performance, and security, delivering concrete feedback and change requests.

Core Features & Use Cases

  • Phase-guided review workflow (Build Context, Review the Diff) that helps reviewers identify what to inspect.
  • Domain-aware feedback: checks correctness, domain correctness, code quality, testing, performance, and security.
  • Use Case: When asked to review a PR, generate structured comments with actionable change requests and benchmarking considerations.

Quick Start

Provide the PR description and diff to begin a thorough, structured review.

Frequently Asked Questions about review

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

FAQPage Schema
How do I perform a structured pull request review for code correctness and security?▼

A structured pull request review evaluates code diffs against correctness, domain logic, quality, testing, performance, and security criteria. This approach enforces context gathering from the PR description and linked tickets to deliver actionable change requests.

Can I review an entire repository's codebase for quality, or is this only for specific PR diffs?▼

This structured code review process applies specifically to evaluating a targeted pull request diff, not the entire repository. It focuses on correctness and domain logic across the changed files to provide precise, actionable feedback.

What is the best way to ensure PR reviews include actionable feedback with proper context?▼

The best way to ensure actionable PR feedback is to follow a phase-guided workflow that builds context from the PR description and linked tickets before reviewing the diff. This generates structured comments with precise file and line references and benchmarking considerations.

How do I check domain correctness and security vulnerabilities during a code review?▼

Checking domain correctness and security vulnerabilities during a code review involves applying a structured evaluation framework to the pull request diff. This domain-aware approach systematically inspects changes for logic flaws, quality issues, and security risks.

What context do I need to provide to start a thorough diff analysis for a pull request?▼

To start a thorough diff analysis, you need to provide the PR description and the code diff. The review workflow uses these inputs to gather context from linked tickets, ensuring the resulting feedback accurately addresses the domain logic and change requests.