review-pr

Review GitHub Pull Request diffs with parallel audit subagents.

5|1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/TalonT-Org/AutoSkillit --skill review-pr-talont-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/TalonT-Org/AutoSkillit/tree/main/src/autoskillit/skills/review-pr
Command: npx skills add https://github.com/TalonT-Org/AutoSkillit --skill review-pr-talont-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of code review for GitHub Pull Requests, ensuring code quality and adherence to standards before merging.

Core Features & Use Cases

  • Diff-Scoped Audits: Reviews only the changes introduced in a PR, focusing on specific dimensions like architecture, tests, bugs, and code style.
  • Inline Commenting: Posts findings directly as inline comments on the PR for easy developer feedback.
  • Automated Verdicts: Provides a clear verdict (approved, changes requested, needs human) based on the review findings.
  • Use Case: Integrate this skill into your CI/CD pipeline to automatically gate PRs, catch common errors, and maintain code health without manual reviewer fatigue.

Quick Start

Use the review-pr skill to review the pull request targeting the main branch from the feature branch.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automate code review for GitHub pull requests?

Automated code review for GitHub pull requests is executed by running diff-scoped audits that evaluate architecture, tests, bugs, and style. The system posts inline comments directly on the PR and submits a summary verdict to gate merging.

How does automated PR review work with GitHub Actions in CI/CD?

Automated PR review in CI/CD uses parallel audit subagents to analyze the diff between feature and base branches. It leverages the GitHub CLI for PR operations, posting inline comments and a summary verdict to gate merges.

What dimensions are covered when auditing pull request diffs?

Auditing pull request diffs covers dimensions including architecture, tests, bugs, and code style. The review focuses exclusively on the changes introduced in the PR, identifying issues and posting findings as inline comments.

Do I need specific branch arguments to review a pull request?

Yes, reviewing a pull request requires specific arguments for the feature and base branches. These branch inputs define the diff scope for the parallel audit subagents to analyze before posting inline comments and a verdict.

What verdicts can an automated code review system provide on a PR?

An automated code review system provides verdicts such as approved, changes requested, or needs human based on the findings. This summary verdict helps gate PRs in CI/CD pipelines to maintain code health without manual reviewer fatigue.