pr-feedback

pr-feedback is a skill for Claude Code from Zate/cc-plugins. It costs 26 tokens per session (1,124 once invoked), scanned A, original, MIT.

A tool that reads comments on a GitHub pull request, which is a proposed code change for review, and turns useful feedback into tasks in a development plan.

In plain words
What is it for?
Use it after a pull-request review to identify requested changes, record who made them, and track related files or lines.
Why use it?
It prevents review comments from being lost or handled informally. Review concerns, suggestions, questions, and smaller notes are organized for follow-up.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the devloop plugin — 19 skills, 6 agents shipped together

Good fit Use it after a pull-request review to identify requested changes, record who made them, and track related files or lines.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zate/cc-plugins/pr-feedback
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Zate/cc-plugins --skill pr-feedback
Clone the repo
git clone --depth 1 https://github.com/Zate/cc-plugins

Made for: Claude Code.

Or install devloop, the plugin that ships this one along with the rest of its 19 skills, 6 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for pr-feedback

README.md
[![agentmods](https://agentmods.dev/badge/skills/zate/cc-plugins/pr-feedback/github.svg)](https://agentmods.dev/skills/zate/cc-plugins/pr-feedback)
Your own site
<a href="https://agentmods.dev/skills/zate/cc-plugins/pr-feedback"><img src="https://agentmods.dev/badge/skills/zate/cc-plugins/pr-feedback/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for pr-feedback

Your own site · 80×15
<a href="https://agentmods.dev/skills/zate/cc-plugins/pr-feedback"><img src="https://agentmods.dev/badge/skills/zate/cc-plugins/pr-feedback.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,124 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.01124
Opus 5.5 $0.00010 $0.00450
Sonnet 5.5 $0.00005 $0.00225
Haiku 4.5 $0.00003 $0.00112

Measured 1mo ago against content hash 1fbfd255ae49, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pr-feedback scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/devloop/skills/pr-feedback/SKILL.md · 209 lines

How it starts

The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PR Feedback - Integrate Review Comments

Fetch PR review feedback and add actionable items to the plan. You do the work directly.

Step 1: Identify PR

If PR number provided: Use $ARGUMENTS

Otherwise, detect from current branch:

gh pr view --json number,title,state,reviewDecision

If no PR found for current branch, inform user and exit.

Step 2: Fetch Feedback

Get PR details:

gh pr view --json number,title,body,reviews,reviewDecision,comments

Get inline code comments:

gh api repos/{owner}/{repo}/pulls/{number}/comments --jq '.[] | {path, line, body, user: .user.login}'

Step 3: Parse Comments

Categorize each comment:

Pattern Category
Review state = CHANGES_REQUESTED Blocker
"must", "need to", "please fix" Blocker
"should", "consider", "might" Suggestion
"why", "what if", "?$" Question
"nit", "minor", "optional" Nitpick

Extract actionable items:

For each comment/review body:

  1. Check if it requests action
  2. Summarize the request
  3. Note the author
  4. Track file/line if inline comment

Step 4: Present Findings

Display to user:

## PR #123 Feedback

**Status**: CHANGES_REQUESTED by @reviewer

### Blockers (must address)
1. Fix null handling in parseConfig (src/config.ts:42)
2. Add tests for edge cases

### Suggestions
3. Consider caching the parsed config

### Questions (respond or address)
4. Why not use the existing parser?

### Nitpicks (optional)
5. Rename variable for clarity

Ask which to add to plan:

AskUserQuestion:
  questions:
    - question: "Which feedback items should be added to the plan?"
      header: "Select"
      multiSelect: true
      options:
        - label: "All blockers"
          description: "Add items 1-2"
        - label: "Blockers + suggestions"
          description: "Add items 1-3"
        - label: "All items"
          description: "Add everything"
        - label: "Select individually"
          description: "Choose specific items"

Read the full file on GitHub · 209 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 209 lines · 26 tokens per session scan A 1fbfd255ae49

Subscribe to this mod's changes

pr-feedback is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 1,124 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.