run-pr-review

Collect PR metadata, CI failures, and review threads to generate and post a consolidated review.

1|Updated May 2, 2026
One-click install
npx skills add https://github.com/abeyuya/skills --skill run-pr-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-pr-review
Source: https://github.com/abeyuya/skills/tree/main/plugins/pr-review/skills/run-pr-review
Command: npx skills add https://github.com/abeyuya/skills --skill run-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It eliminates the multi-step effort of preparing context, generating a structured PR review, posting it once, and then tidying up existing review threads.

Core Features & Use Cases

  • End-to-end PR review orchestration: Runs PR context collection, review text generation, review posting, and thread resolution in a single flow.
  • Safe existing-context reuse: Pulls prior review threads to reduce duplicate or redundant inline feedback.
  • CI-aware review assistance: Summarizes failed job log excerpts to inform the review with targeted failure evidence.
  • Use Case: When a PR is ready for review, you can trigger one skill call to produce and post a coherent review while ensuring stale threads are resolved according to your chosen scope.

Quick Start

Run the PR review by calling run-pr-review with the target OWNER, REPO, and PR_NUMBER.

Frequently Asked Questions about run-pr-review

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

FAQPage Schema
How do I automate end-to-end GitHub PR review and resolve existing threads with one command?

An end-to-end GitHub PR review workflow collects PR metadata, existing review thread context, and CI failure log excerpts to generate and post a consolidated review once while optionally resolving prior review threads in a single execution context.

How does CI failure analysis work during automated pull request review orchestration?

CI failure analysis during pull request review orchestration works by summarizing failed job log excerpts, which informs the generated review with targeted evidence of specific failures rather than just inspecting code changes.

What's the best way to prevent misaligned comments when posting automated PR reviews?

Preventing misaligned comments requires validating required inputs and forwarding the head commit id to ensure the automated PR review feedback aligns with the exact state of the pull request.

Can I reuse existing review thread context to avoid duplicate inline feedback on a pull request?

Yes, you can reuse existing review thread context to avoid duplicate inline feedback. The workflow pulls prior review threads to safely reduce redundant comments during new review generation.

What scope options are available when resolving stale PR threads during review orchestration?

When resolving stale PR threads during review orchestration, you can resolve prior threads according to a configured scope, controlling exactly which existing conversations are marked as resolved after posting the new review.