address-pr-feedback

address-pr-feedback is a skill for Claude Code from rp1-run/rp1. It costs 23 tokens per session (1,544 once invoked), scanned A, original, Apache-2.0.

A workflow for collecting, sorting, and fixing comments on a pull request. A pull request is a proposed code change that someone else reviews before it is added to the project.

In plain words
What is it for?
It helps gather pull-request comments, triage them, apply code changes, and report the result.
Why use it?
It brings review comments into one process so issues are not missed between reading feedback, deciding what matters, and making fixes.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the rp1-dev plugin — 23 skills, 36 agents shipped together

Good fit It helps gather pull-request comments, triage them, apply code changes, and report the result.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rp1-run/rp1/address-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 rp1-run/rp1 --skill address-pr-feedback
Clone the repo
git clone --depth 1 https://github.com/rp1-run/rp1

Made for: Claude Code.

Or install rp1-dev, the plugin that ships this one along with the rest of its 23 skills, 36 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 address-pr-feedback

README.md
[![agentmods](https://agentmods.dev/badge/skills/rp1-run/rp1/address-pr-feedback/github.svg)](https://agentmods.dev/skills/rp1-run/rp1/address-pr-feedback)
Your own site
<a href="https://agentmods.dev/skills/rp1-run/rp1/address-pr-feedback"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/address-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 address-pr-feedback

Your own site · 80×15
<a href="https://agentmods.dev/skills/rp1-run/rp1/address-pr-feedback"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/address-pr-feedback.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,544 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.00023 $0.01544
Opus 5.5 $0.00009 $0.00618
Sonnet 5.5 $0.00005 $0.00309
Haiku 4.5 $0.00002 $0.00154

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

Security

Grade A, and why

address-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/dev/skills/address-pr-feedback/SKILL.md · 215 lines

How it starts

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

Unified PR Feedback Workflow

You are PRFeedbackGPT, an expert at systematically collecting and resolving pull request review comments. This command combines collection, triage, and fix phases into a single workflow.

First emit: Generate RUN_ID as a UUID. Derive RUN_NAME from the PR: use "Feedback: PR #{pr_number}" when available, otherwise "Feedback: {branch_name}".

On session start, emit the status change:

rp1 agent-tools emit \
  --workflow address-pr-feedback \
  --type status_change \
  --run-id {RUN_ID} \
  --name "{RUN_NAME}" \
  --step collecting \
  --data '{"status": "running"}'

STATE-MACHINE

stateDiagram-v2
    [*] --> collecting
    collecting --> fixing : triage_complete
    fixing --> [*] : done

State mapping:

  • collecting covers: Phase 1 (collection) + Phase 2 (triage)
  • fixing covers: Phase 3 (fix) + Phase 4 (report)

State Progression Protocol:

  1. Report each --step with --data '{"status": "running"}' when you enter that state
  2. For non-terminal states: move to the NEXT state when done (entering the next state implies the previous completed)
  3. For terminal states (those with → [*] transitions): report with --data '{"status": "completed"}' and --close-run when the step's work finishes

Example sequence:

--workflow address-pr-feedback --step collecting --name "Feedback: PR #42" --data '{"status": "running"}'
--workflow address-pr-feedback --step fixing --data '{"status": "running"}'
--workflow address-pr-feedback --step fixing --data '{"status": "completed"}' --close-run

Phase 1: Collection

Invoke the pr-feedback-collector agent to gather and classify PR comments:

{% dispatch_agent "rp1-dev:pr-feedback-collector" %} FEATURE_ID: {FEATURE_ID or derived from PR} PR_NUMBER: {PR_IDENTIFIER if numeric, else auto-detect} WORK_ROOT: {workRoot} {% enddispatch_agent %}

Wait for collection to complete. The agent produces .rp1/work/pr-reviews/{identifier}-feedback-{NNN}.md.

Read the full file on GitHub · 215 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 · 215 lines · 23 tokens per session scan A 1b8866976b71

Subscribe to this mod's changes

address-pr-feedback is a skill published in the GitHub repository rp1-run/rp1 (38 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 1,544 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-09-07.

Related

Other skills, from other repositories

spec-finish

Post-implementation completion workflow for Spec-backed Plans. Use after spec-implement completes to validate, review, create stacked commits, and open a PR via code-pull-request. Triggers only with an active Spec-backed Plan after spec-implement completes, including when the user says "finish", "done", or "complete"…

martinffx/atelier · 73 tokens

gsd-pr-branch

Create a clean PR branch by filtering out .planning/ commits — ready for code review.

open-gsd/gsd-core · 23 tokens

guardian

Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy; the ship recipe also executes PR delivery (create, CI watch, merge, cleanup) with Ask First on merge. Use when PR preparation, commit strategy, or gated PR delivery is needed.

simota/agent-skills · 62 tokens

github

Manage the full GitHub workflow from the terminal — auth, issues, pull request lifecycle (branch/commit/open/CI/merge), code review, and repo management. Uses the gh CLI when present, with a git + REST API fallback. Use when asked to "open a PR", "create an issue", "review this PR", "check CI", "list issues".

diillson/chatcli · 78 tokens

github-publish-changes

Publish intentional local changes by confirming scope, creating a branch when needed, staging selected files, committing, pushing, and creating a Draft Pull Request through the connected GitHub service.

Devin-AXIS/iPolloWork · 41 tokens

code-commit

Generate and validate conventional commit messages following the conventionalcommits.org spec. Use whenever the user wants to commit code, mentions commit messages, git commit, or asks to create a commit. Triggers on "commit", "git commit", "conventional", or when reviewing commit message format.

martinffx/atelier · 62 tokens