respond-pr

Fetch GitHub PR comment threads and generate typed replies.

4|1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/jcdendrite/claude-config --skill respond-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: respond-pr
Source: https://github.com/jcdendrite/claude-config/tree/main/claude/.claude/skills/respond-pr
Command: npx skills add https://github.com/jcdendrite/claude-config --skill respond-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you systematically respond to review comments on your current branch’s open pull request without missing comment types, posting malformed replies, or accidentally editing the wrong threads.

Core Features & Use Cases

  • Fetches all review inputs across inline file comments, top-level review comments, and issue-level comments to avoid truncated or incomplete triage.
  • Validates PR state before changes by checking the PR for merge conflicts against the base branch before applying any FIXED work or posting replies.
  • Batches triage and commits so code changes land once (single commit) before replies, keeping diffs aligned with what reviewers see.
  • Enforces disciplined reply structure including the required attribution prefix and typed dispositions (FIXED, EXPLAIN-DESIGN, OUT-OF-SCOPE, DEFERRED, AGREE-NO-CHANGE).

Quick Start

Ask the AI to run the respond-pr skill for your current branch’s open PR, replying to all unread review comments on GitHub.

Frequently Asked Questions about respond-pr

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

FAQPage Schema
How do I reply to GitHub pull request review comments automatically?

Automating GitHub pull request review replies involves fetching inline, review, and issue-level comment threads, triaging them with typed dispositions, and posting responses via the GitHub API endpoints to ensure no comments are missed.

What is the best way to triage unread PR comments before posting replies?

The best way to triage unread PR comments is to batch them with typed dispositions like FIXED, EXPLAIN-DESIGN, OUT-OF-SCOPE, or DEFERRED. This categorizes feedback before applying any code changes or generating reply text.

How do merge conflicts affect automated PR review reply workflows?

Merge conflicts halt automated PR review reply workflows by triggering a divergence precheck against the base branch. This validation prevents the application of FIXED code changes or the posting of replies until conflicts are resolved.

Can I commit code changes and reply to PR review comments in a single step?

Yes, you can commit code changes and reply to PR review comments together by batching triage and applying a single commit for any FIXED work before posting replies. This keeps the diff aligned with what reviewers see.

Does automated PR reply posting require git hooks to function?

Automated PR reply posting requires hook-marker based gating to function correctly. This mechanism ensures the workflow only triggers when conversation context matches the targeted pull request and unread comments exist.

Why do my automated GitHub replies get posted to the wrong comment threads?

Automated GitHub replies get posted to the wrong threads when the system lacks strict reply structure enforcement or proper endpoint targeting. Enforcing correct GitHub API reply endpoints and attribution prefixes prevents malformed or misplaced responses.