review

Review pull requests through a structured 6-phase process.

6|Updated Aug 3, 2025
One-click install
npx skills add https://github.com/foomakers/pair --skill review-foomakers
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/foomakers/pair/tree/main/packages/knowledge-hub/dataset/.skills/process/review
Command: npx skills add https://github.com/foomakers/pair --skill review-foomakers

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex and time-consuming process of code review, ensuring adherence to quality standards, project adoption guidelines, and completeness criteria, thereby accelerating the development cycle.

Core Features & Use Cases

  • Structured Review Process: Guides through validation, technical review, adoption compliance, completeness checks, and decision-making.
  • Automated Skill Composition: Leverages atomic skills like /verify-quality, /verify-done, and /assess-debt for comprehensive analysis.
  • Idempotent Execution: Can be re-invoked to resume incomplete reviews or re-evaluate after changes without starting over.
  • Use Case: A developer submits a pull request. The /review skill automatically checks code quality, verifies against project standards, flags technical debt, and compiles a detailed report, allowing the reviewer to focus on high-level feedback and decision-making.

Quick Start

Use the review skill to review pull request number 123.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review for a pull request?▼

Automating code review for a pull request involves running a structured 6-phase process that validates code, assesses technical debt, and checks project compliance. This skill compiles a detailed report to accelerate the development workflow.

What is the best way to check technical debt during development workflow?▼

Checking technical debt during development workflow is handled by an automated assessment phase that evaluates the code against project standards. It identifies debt and compliance issues to ensure quality assurance before merging.

Can I resume an incomplete code review after making changes?▼

Resuming an incomplete code review is supported through idempotent execution. You can re-invoke the process to evaluate changes without starting over, ensuring graceful degradation if the review was interrupted.

Does the automated pull request review verify completeness criteria?▼

Yes, automated pull request review explicitly verifies completeness criteria. It runs checks against project adoption guidelines and story requirements to ensure all conditions are met before final decision-making.

How does the code review process handle parent cascade merging?▼

The code review process handles parent cascade merging by integrating optional merge validation into its phases. It ensures idempotency and graceful degradation when evaluating pull requests against parent branches.

What are the limitations of automating quality assurance for pull requests?▼

Limitations of automating quality assurance include reliance on predefined project adoption guidelines and atomic skill composition. It requires structured input stories to function correctly and cannot review unstructured code changes effectively.