review-skill

review-skill is a skill for Claude Code from Azzygoatcoder/agent-useful-skills. It costs 89 tokens per session (661 once invoked), scanned A, original, MIT.

A workflow for reviewing GitHub pull requests, which are proposed changes submitted for discussion and merging into a codebase.

In plain words
What is it for?
It helps read pull requests and diffs, request changes, approve or comment on them, merge them, or close them.
Why use it?
It organizes the steps from inspecting a change to giving a formal decision, so reviews are not handled inconsistently.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the dev-workflow plugin — 4 skills shipped together

Good fit It helps read pull requests and diffs, request changes, approve or comment on them, merge them, or close them.

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

Made for: Claude Code.

Or install dev-workflow, the plugin that ships this one along with the rest of its 4 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 review-skill

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/azzygoatcoder/agent-useful-skills/review-skill"><img src="https://agentmods.dev/badge/skills/azzygoatcoder/agent-useful-skills/review-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 89 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 661 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.00089 $0.00661
Opus 5 $0.00044 $0.00331
Sonnet 5 $0.00018 $0.00132
Haiku 4.5 $0.00009 $0.00066

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

Security

Grade A, and why

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

plugins/dev-workflow/skills/review-skill/SKILL.md · 44 lines

What it actually says

Review — GitHub PR Review 工作流

评审者动作:看 PR → 评审 → 提交 approve/changes → 合并。与 pr-skill(作者提 PR)相对。

角色

本 skill 是「评审者」的 = 有 merge 权限的 maintainer / owner。作者侧走 pr-skill;代码质量评审按场景 B 委托通用 code-review 流程。

场景判定

场景 触发 动作
A. 看 PR "看这个 PR" / "review #N" gh pr view + gh pr diff
B. 评审代码 判断质量 委托 code-review skill(找 bug + 复用/简化/效率)
C. 提交评审 "approve" / "要求改" / "评论" gh pr review --approve/--request-changes/--comment
D. 合并 "合了" / "merge" gh pr merge --merge/--squash/--rebase

流程

  1. 看 PRgh pr view <N> 读标题/正文/变更文件;gh pr diff <N> 读 diff
  2. 评代码质量:委托 code-review skill(找 bug + 复用/简化/效率清理);意见按严重度分
  3. 提交评审
    gh pr review <N> --approve                        # 通过
    gh pr review <N> --request-changes --body "..."   # 要求改(列具体点,别空泛)
    gh pr review <N> --comment --body "..."           # 仅评论,不表态
    
  4. 合并(approve 后):
    gh pr merge <N> --merge      # 或 --squash / --rebase,按团队规范
    gh pr close <N>              # 不合并就关
    

自进化日志

日期 学习来源 吸收的模式
2026-08-13 协作流梳理(pr/release/issue 之后补 review) review 是「评审者」的 skill(有 merge 权限),与 pr-skill 作者侧相对;代码质量委托 code-review skill,本 skill 只管 GitHub 机制(approve/changes/merge)
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 · 44 lines · 89 tokens per session scan A bdce077f7fe7

Subscribe to this mod's changes

review-skill is a skill published in the GitHub repository Azzygoatcoder/agent-useful-skills (6 stars, last pushed 12d ago), licensed MIT. It adds 89 tokens to every session and 661 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

comet-github-pr-review

A read-only review process for pull requests in Comet's GitHub repositories. A pull request is a proposed code change; the review checks its current code, related issue, comments, merge status, and automated checks.

rpamis/comet · 69 tokens

resolve-pr-comments

Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments. Handles both change requests (fix or skip) and reviewer questions (explain using reasoning recalled from past Claude Code transcripts). Use when the user asks to "resolve PR comments", "fix review comments", "address PR…

tobihagemann/turbo · 95 tokens

fetch-pr-comments

Fetch and summarize review feedback and conversation from a GitHub PR (unresolved review threads, review bodies, and PR conversation comments) without making changes. Use when the user asks to "fetch PR comments", "show PR comments", "check PR for unresolved comments", "list review comments", "what comments are on the…

tobihagemann/turbo · 83 tokens

reply-to-pr-threads

Draft, confirm, and post replies to GitHub PR review threads. Handles per-category reply formatting, re-fetches thread resolution state so auto-resolved threads are skipped, and posts via GraphQL. Use when the user asks to "reply to PR threads", "post PR thread replies", or "draft PR reply messages".

tobihagemann/turbo · 71 tokens

reply-to-pr-conversation

Draft, confirm, and post a single conversational reply to GitHub PR conversation comments (issue comments). The reply addresses all tracked items in one natural-prose message. Use when the user asks to "reply to PR conversation", "post PR conversation replies", or "draft PR conversation messages".

tobihagemann/turbo · 64 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens