review-pr

Fetch GitHub PR details and unresolved threads to generate structured feedback.

1|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/specvital/infra --skill review-pr-specvital
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/specvital/infra/tree/main/.claude/skills/review-pr
Command: npx skills add https://github.com/specvital/infra --skill review-pr-specvital

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the review of GitHub Pull Requests by identifying and evaluating unresolved review comments, enabling faster, more thorough feedback.

Core Features & Use Cases

  • Fetch PR metadata and unresolved threads using gh pr view and a GraphQL query.
  • Filter only unresolved threads (isResolved: false) and verify if issues still exist in current code.
  • Provide structured feedback including file paths, line context, assessment, and recommended fixes.

Quick Start

Run the skill against a PR URL to begin the review.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automate GitHub PR review for unresolved comments?

Automate GitHub PR review by fetching metadata and unresolved threads with gh pr view and GraphQL, then filtering isResolved: false to generate actionable codebase feedback.

What's the best way to check unresolved threads in a GitHub pull request?

Check unresolved threads in a GitHub pull request by running a GraphQL query to filter isResolved: false, verifying reported issues against current files, and outputting structured fix guidance.

Does gh-cli support filtering unresolved review comments on a PR?

Yes, gh-cli supports filtering unresolved review comments by executing gh api graphql with an external query to fetch threads where isResolved is false, reading files for context to validate issues.

Can I verify if unresolved PR review issues still exist in the current codebase?

Yes, you can verify unresolved PR review issues by fetching unresolved threads via GraphQL, reading the referenced file paths for context, and assessing whether the reported problems persist in the current code.

How do I generate structured feedback for unresolved GitHub PR threads?

Generate structured feedback for unresolved GitHub PR threads by fetching unresolved comments, verifying them against current code context, and outputting actionable guidance with file paths, line context, and recommended fixes.