review-pull-requests

Validate pull request metadata and generate structured readiness reports.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/ourchitecture/idp --skill review-pull-requests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pull-requests
Source: https://github.com/ourchitecture/idp/tree/main/.agents/skills/review-pull-requests
Command: npx skills add https://github.com/ourchitecture/idp --skill review-pull-requests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews are time-consuming and error-prone when done manually; this skill automates checks for metadata completeness, linkage to issues, CI status, and merge-readiness to accelerate high-quality reviews.

Core Features & Use Cases

  • Validate PR metadata (title, body, labels) against repository conventions.
  • Verify linked issues, commit history, and change impact against scope.
  • Generate a structured findings report with an overall status, merge readiness, and scoring for decision support.

Quick Start

Provide a PR number to the review skill to generate a comprehensive findings report.

Frequently Asked Questions about review-pull-requests

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

FAQPage Schema
How do I automate GitHub PR reviews for quality and merge-readiness?

Automate GitHub PR reviews by validating metadata, linked issues, commit history, and CI status against repository conventions. The skill surfaces actionable findings and generates a structured report with an overall status, merge readiness flag, and quality score for decision support.

What checks are applied during automated code review of a pull request?

Automated pull request checks validate the PR title, body, and labels, verify linked issues, analyze commit history and changed files, and check CI status. This determines overall readiness and quality, producing structured findings, a merge_ready flag, and a score.

Does this automated PR validation work with existing CI pipelines on GitHub?

Yes, the validation process checks CI status as part of its automated review. It applies checks to the PR metadata, linked issues, commit history, changed files, and CI status to determine merge readiness and generate a structured findings report for reporting.

What is the best way to validate pull request metadata against repository conventions?

The best way to validate PR metadata is to provide a PR number to the review skill. It automatically validates the title, body, and labels against repository conventions and generates a comprehensive findings report with merge readiness and scoring.

Why does my automated pull request review return a low quality score?

A low quality score indicates the PR failed validation checks against repository conventions. The skill identifies PR metadata gaps, missing linked issues, commit history inconsistencies, changed file impacts, or CI status failures, surfacing these as actionable findings in the report.

Do I need a specific PR number to start automating code review validation?

Yes, you provide a PR number to generate a comprehensive findings report. The skill uses this number to fetch metadata, validate it against repository conventions, check CI status, and produce an overall status, merge_ready flag, and score.