address-review

address-review is a skill for Claude Code from saffron-health/libretto. It costs 21 tokens per session (451 once invoked), scanned A, original, MIT.

A process for handling review comments on a GitHub pull request, a proposed set of code changes. It retrieves the comments, applies and checks the requested fixes, and can commit, push, and resolve addressed discussion threads.

In plain words
What is it for?
Use it to address pull-request comments, run type checks, builds, and linting, then update the branch and close completed review discussions.
Why use it?
It turns scattered review feedback into a tracked sequence of code changes and verification steps.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents; installed under .agents/ (shared by several agents).

Part of the libretto plugin — 24 skills shipped together

Good fit Use it to address pull-request comments, run type checks, builds, and linting, then update the branch and close completed review discussions.

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

Made for: Claude Code.

Or install libretto, the plugin that ships this one along with the rest of its 24 skills.

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-review

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/saffron-health/libretto/address-review"><img src="https://agentmods.dev/badge/skills/saffron-health/libretto/address-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 451 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00021 $0.00451
Opus 5 $0.00010 $0.00226
Sonnet 5 $0.00004 $0.00090
Haiku 4.5 $0.00002 $0.00045

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

Security

Grade A, and why

address-review 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 11d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.agents/skills/address-review/SKILL.md · 44 lines

What it actually says

Address PR review comments systematically.

Process

  1. Get review comments: Use gh api graphql to fetch all review threads and comments for the PR. (If a PR number is not provided in the input, look up the PR for the current branch).

  2. Analyze comments: Review all the feedback to understand what changes are needed

  3. Address each comment systematically: For each review comment:

    • Make the requested code changes
    • Verify the changes fix the issue raised
    • Add explanatory comments if the reviewer requested clarification
    • Test changes to ensure they don't break existing functionality
  4. Quality assurance: Run type-check, build, and lint to ensure all changes are correct

  5. Commit and push: Stage and commit all changes with an appropriate message and push.

  6. Mark comments resolved: Query PR review threads with gh api graphql to get thread IDs and outdated status. Resolve all addressed threads using mutation { resolveReviewThread(input: {threadId: "THREAD_ID"}) { thread { isResolved } } }. Always resolve outdated threads.

Implementation Pattern

// Query review threads:
gh api graphql -f query='query { repository(owner: "owner", name: "repo") { pullRequest(number: N) { reviewThreads(first: 100) { nodes { id isResolved isOutdated comments { nodes { body } } } } } } }'

// Resolve thread:
gh api graphql -f query='mutation { resolveReviewThread(input: {threadId: "THREAD_ID"}) { thread { isResolved } } }'

Notes

  • Only address reviews from human users; ignore bot reviews (e.g., Claude) unless explicitly requested
  • Use sub-agents to handle independent review comments in parallel when possible
  • Always verify changes don't introduce new issues
  • If a review comment requires clarification, document the approach taken
  • Focus on the specific issues raised rather than making additional changes
  • Mark outdated comments as resolved automatically since they no longer apply to current code
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. 11d ago First seen · 44 lines · 21 tokens per session scan A ba07c4f389ee

Subscribe to this mod's changes

address-review is a skill published in the GitHub repository saffron-health/libretto (889 stars, last pushed 21d ago), licensed MIT. It adds 21 tokens to every session and 451 once invoked, about $0.0001 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-30.

Related

Other skills, from other repositories

hyperflow-audit

Hyperflow code review. Use when the user wants the current diff, a commit, branch, or PR reviewed — verbs like audit, review, "check for issues", "security check", "code review". Multi-level review (L1 quick → L5 exhaustive), writes findings to .hyperflow/audits/, then a fix-gate.

jeremylongshore/tons-of-skills-marketplace · 75 tokens

pr-review

Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.

oliver-kriska/claude-elixir-phoenix · 59 tokens

phx-pr-review

Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.

oliver-kriska/claude-elixir-phoenix · 61 tokens

pr-threshold

Track commit accumulation and trigger PR when thresholds crossed.

WellApp-ai/Well · 13 tokens

no-mistakes

Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.

stevesolun/ctx · 67 tokens

code-review-github

GitHub PR workflow orchestration for code review — list PRs, post comments, apply labels, and guarded auto-merge.

initializ/forge · 30 tokens