review-respond

Batch-process pending GitHub PR review comments and apply fixes.

3.7k|104|Updated Dec 11, 2020
One-click install
npx skills add https://github.com/dathere/qsv --skill review-respond
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-respond
Source: https://github.com/dathere/qsv/tree/main/.claude/skills/review-respond
Command: npx skills add https://github.com/dathere/qsv --skill review-respond

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Batch-process pending PR review comments across a repository, automating retrieval, triage, and reply to speed up review cycles.

Core Features & Use Cases

  • Identify the target PR (provided number or detect the current PR) and prepare a unified review workflow.
  • Fetch all pending review comments and unresolved threads from the PR to centralize feedback handling.
  • Route comments by reviewer type (Copilot vs human) and automatically apply safe fixes where possible.
  • Verify changes, run tests, commit results, and post replies with a concise summary.
  • Use cases include addressing Copilot-generated feedback, human reviewer threads, and batch-closure of review cycles.

Quick Start

Provide the PR number to begin automatically processing all pending review comments.

Frequently Asked Questions about review-respond

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

FAQPage Schema
How do I automate responses to pending PR review comments on GitHub?

Automating GitHub PR review responses involves batch-fetching pending comments, triaging them by reviewer type, applying fixes, running tests, and committing results with a summary reply.

Does this workflow handle both Copilot and human reviewer comments?

Yes, the workflow routes comments by reviewer type, distinguishing between Copilot and human reviewers to apply safe fixes automatically across unresolved threads.

What do I need to batch-process pull request review feedback automatically?

Batch-processing PR review feedback requires GitHub API access, gh CLI utilities, and proper repository permissions to fetch, triage, verify, and post replies on pull requests.

Can I apply fixes and run tests before committing automated PR review replies?

Yes, the workflow verifies applied code changes and runs tests before committing results and posting concise summary replies to close the review cycle.

What is the best way to handle unresolved PR review threads across a repository?

Handling unresolved PR threads centrally involves fetching all pending review comments, applying safe automated fixes, verifying changes, and posting batch replies to speed up review cycles.