pair-process-review

Review pull requests through a structured 6-phase process with validation and decision making.

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

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 reviews, ensuring quality, consistency, and adherence to project standards.

Core Features & Use Cases

  • Structured Review Process: Guides AI through a 6-phase review (validation, technical, adoption, completeness, decision, merge).
  • Automated Compliance Checks: Verifies code against quality gates, adoption standards, and definition of done.
  • Use Case: When a developer submits a pull request, this Skill can automatically perform a comprehensive review, identify potential issues, flag technical debt, and even suggest a merge decision, significantly speeding up the development cycle.

Quick Start

Use the pair-process-review skill to review pull request number 123.

Frequently Asked Questions about pair-process-review

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

FAQPage Schema
How do I automate code reviews for pull requests?

Automate pull request code reviews by running a structured 6-phase process that handles validation, technical assessment, adoption compliance, completeness checks, and decision making to deliver detailed reports and optional merging.

Can I automate quality assurance and compliance checks during a pull request review?

Yes, automated compliance checks verify code against quality gates, adoption standards, and the definition of done, flagging technical debt and potential issues during the pull request review.

What is the best way to structure an automated pull request review process?

The best way to structure an automated pull request review is using a 6-phase process: validation, technical assessment, adoption compliance, completeness checks, decision making, and optional merging.

Does this automated code review tool handle re-invocation if the pull request state changes?

Yes, the review process supports idempotent re-invocation, allowing it to safely execute again on the same pull request while gracefully degrading for any missing capabilities.

How do I get a merge decision suggestion from an automated code review?

The decision making phase of the review process evaluates technical assessment and compliance results to suggest a merge decision, significantly speeding up the development cycle.