pr-review

Review pull requests against issue specifications and quality standards.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the comprehensive review of pull requests, ensuring alignment with specifications, architectural standards, testing policies, and documentation requirements without making code changes.

Core Features & Use Cases

  • Spec Alignment: Verifies PRs against linked issue specifications.
  • Quality Assurance: Checks architecture, testing posture, and documentation consistency.
  • Findings Reporting: Clearly categorizes issues by severity with precise location references.
  • Use Case: A developer submits a PR. This Skill reviews it against the issue spec, checks if new tests were added appropriately, and ensures documentation is updated, providing a structured report before human review.

Quick Start

Use the pr-review skill to review pull request number 123.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I automate code review for a GitHub pull request against issue specifications?

Automate code review by using a Skill that checks pull requests against linked issue specifications, architectural standards, and testing policies. It identifies findings by severity with path:line references and can submit formal GitHub reviews.

Does automated PR review check if documentation and tests were updated?

Yes, automated PR review verifies quality assurance by checking architecture, testing posture, and documentation consistency. It ensures new tests are added appropriately and documentation is updated before providing a structured report.

Do I need GitHub CLI to review pull requests for spec and arch alignment?

Yes, you need GitHub CLI installed and configured to interact with repositories and submit formal GitHub reviews. The review process also requires specific documentation files for context to verify spec and arch alignment.

What is the best way to report code review findings with precise location references?

Report code review findings by categorizing issues by severity with precise path:line references. This structured reporting approach clearly identifies architectural, testing, and documentation issues for developers before human review.

Can I use GitHub Actions to review pull requests for testing posture and documentation?

Yes, you can integrate PR review into GitHub Actions workflows to automatically review pull requests for testing posture and documentation. It verifies alignment with issue specifications and project constraints without making code changes.

Why does PR review report findings by severity instead of just failing the check?

PR review reports findings by severity to provide a structured report that categorizes issues by impact level with path:line references. This allows developers to prioritize fixes before human review, rather than simply failing without context.