organizing-pr-feedback

organizing-pr-feedback is a skill for Claude Code, Codex from karashiiro/agent-skills. It costs 40 tokens per session (943 once invoked), scanned A, original, Unlicense.

A guide for collecting and sorting comments from a GitHub pull request, which is a proposed code change submitted for review.

In plain words
What is it for?
Use it to prepare an actionable revision checklist after a pull request review.
Why use it?
It brings discussion comments and code-specific review threads into one list and separates resolved items from work still needed.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to prepare an actionable revision checklist after a pull request review.

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

Made for: Claude Code, Codex.

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 organizing-pr-feedback

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/karashiiro/agent-skills/organizing-pr-feedback"><img src="https://agentmods.dev/badge/skills/karashiiro/agent-skills/organizing-pr-feedback.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 943 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.00040 $0.00943
Opus 5 $0.00020 $0.00472
Sonnet 5 $0.00008 $0.00189
Haiku 4.5 $0.00004 $0.00094

Measured 10d ago against content hash 68c78b3c645f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

organizing-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 10d 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.

organizing-pr-feedback/SKILL.md · 133 lines

How it starts

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

Organizing PR Feedback

Overview

Collect all feedback threads from a GitHub PR, cross-reference author replies to identify resolved vs. open items, and produce a consolidated revision table grouped by topic.

When to Use

  • Reviewing or organizing PR comments
  • Identifying what still needs addressing after reviews
  • Preparing a revision pass

Fetching PR Feedback via Gateway

Issue-level comments (general discussion)

local comments = github.issue_read({
  owner = "OWNER",
  repo = "REPO",
  issue_number = PR_NUMBER,
  method = "get_comments",
  perPage = 100
}):await()

local out = {}
for _, c in ipairs(comments.comments or {}) do
  table.insert(out, {
    id = c.id,
    author = c.user and c.user.login or "unknown",
    created = c.created_at,
    body = c.body
  })
end
result(out)

Inline review threads (code-level comments)

local res = github.pull_request_read({
  method = "get_review_comments",
  owner = "OWNER",
  repo = "REPO",
  pullNumber = PR_NUMBER,
  perPage = 100
}):await()

local threads = {}
if res.review_comments and res.review_comments.reviewThreads then
  for _, thread in ipairs(res.review_comments.reviewThreads) do
    local t = {
      isResolved = thread.IsResolved,
      isOutdated = thread.IsOutdated,
      path = nil,
      comments = {}
    }
    if thread.Comments and thread.Comments.Nodes then
      for _, c in ipairs(thread.Comments.Nodes) do
        table.insert(t.comments, {
          author = c.Author and c.Author.Login or "unknown",
          body = c.Body,
          path = c.Path,
          line = c.Line
        })
        t.path = t.path or c.Path
      end
    end
    table.insert(threads, t)
  end
end
result(threads)

Note: Review thread fields use PascalCase (GraphQL style): IsResolved, Comments.Nodes, Author.Login, Body, Path, Line.

Top-level reviews (approve/request-changes verdicts)

local res = github.pull_request_read({
  method = "get_reviews",
  owner = "OWNER",
  repo = "REPO",
  pullNumber = PR_NUMBER,
  perPage = 100
}):await()

local reviews = {}
for _, r in ipairs(res.reviews or {}) do
  table.insert(reviews, {
    author = r.user and r.user.login or "unknown",
    state = r.state,
    body = r.body
  })
end
result(reviews)

Read the full file on GitHub · 133 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. 10d ago First seen · 133 lines · 40 tokens per session scan A 68c78b3c645f

Subscribe to this mod's changes

organizing-pr-feedback is a skill published in the GitHub repository karashiiro/agent-skills (2 stars, last pushed 4mo ago), licensed Unlicense. It adds 40 tokens to every session and 943 once invoked, about $0.0002 per session on Opus 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.