receiving-pr-feedback

Processes PR review comments with verification and controlled responses for multiple PRs.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/ckallum/calsuite --skill receiving-pr-feedback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-pr-feedback
Source: https://github.com/ckallum/calsuite/tree/main/.claude/skills/receiving-pr-feedback
Command: npx skills add https://github.com/ckallum/calsuite --skill receiving-pr-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Handle PR review feedback with technical rigor. Verify suggestions before implementing, push back when they're wrong, and never blindly agree. Multi-PR mode supports spawning separate Claude Code instances per PR.

Core Features & Use Cases

  • Multi-PR Mode: spawn per-PR Claude Code contexts to isolate feedback workflows.
  • Load feedback: fetch inline review comments and top-level PR discussions for each PR.
  • Classify feedback: categorize comments by type (bug, style, architecture, questions, nitpicks, outdated).
  • Process and respond: verify changes before applying, push back with rationales, and answer clarifications.
  • Update PR description: automatically update revision history and summary sections after fixes.

Quick Start

Invoke the skill with a PR number or comma-separated PR numbers to start loading and processing review feedback.

Frequently Asked Questions about receiving-pr-feedback

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

FAQPage Schema
How do I automatically process pull request review feedback and reply to inline comments?

To automatically process pull request review feedback, this Skill loads PR inline comments and top-level discussions, classifies them by type, and generates per-comment responses by either applying approved changes or pushing back with technical justification.

How does multi-PR code review handling work for separate pull requests?

Multi-PR code review handling works by spawning isolated Claude Code contexts for each pull request, allowing you to load, classify, and respond to feedback across multiple PRs simultaneously without cross-contamination of review workflows.

Can I automatically classify code review comments into categories like bugs, style issues, or nitpicks?

Yes, you can automatically classify code review comments into categories including bug, style, architecture, questions, nitpicks, and outdated, enabling targeted processing and appropriate responses for each type of pull request feedback.

What is the best way to push back on incorrect PR review suggestions with technical justification?

The best way to push back on incorrect PR review suggestions is to verify each comment's technical validity before applying changes, then generate a justified rationale explaining why the suggestion is wrong instead of blindly agreeing to the feedback.

How do I update a pull request description revision history after addressing code review feedback?

Updating a pull request description revision history happens automatically after fixes are applied, revising the summary and revision history sections to reflect the changes made in response to the classified PR review feedback.

Does this PR feedback handling approach work without external dependencies or additional components?

Yes, this PR feedback handling approach works without external dependencies or additional components, requiring only a PR number or comma-separated PR numbers to begin loading and processing review feedback from your repository.