rescue__pull_request_review

rescue__pull_request_review is a skill for Claude Code, Codex from shunsock/dotfiles. It costs 104 tokens per session (2,339 once invoked), scanned A, original, no licence file.

An automated workflow for handling GitHub pull-request review comments, applying requested code changes, committing them, and pushing them back.

In plain words
What is it for?
Use it to process reviewer feedback on a pull request and update the branch after each review round.
Why use it?
It removes the need to repeat the same review-response steps manually after each round of comments.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing. Also seen: model in frontmatter.

Good fit Use it to process reviewer feedback on a pull request and update the branch after each review round.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/shunsock/dotfiles/rescue__pull_request_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 shunsock/dotfiles --skill rescue__pull_request_review
Clone the repo
git clone --depth 1 https://github.com/shunsock/dotfiles

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 rescue__pull_request_review

README.md
[![agentmods](https://agentmods.dev/badge/skills/shunsock/dotfiles/rescue__pull_request_review/github.svg)](https://agentmods.dev/skills/shunsock/dotfiles/rescue__pull_request_review)
Your own site
<a href="https://agentmods.dev/skills/shunsock/dotfiles/rescue__pull_request_review"><img src="https://agentmods.dev/badge/skills/shunsock/dotfiles/rescue__pull_request_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 rescue__pull_request_review

Your own site · 80×15
<a href="https://agentmods.dev/skills/shunsock/dotfiles/rescue__pull_request_review"><img src="https://agentmods.dev/badge/skills/shunsock/dotfiles/rescue__pull_request_review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 104 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,339 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 unknown 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.00104 $0.02339
Opus 5.5 $0.00042 $0.00936
Sonnet 5.5 $0.00021 $0.00468
Haiku 4.5 $0.00010 $0.00234

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

Security

Grade A, and why

rescue__pull_request_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 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.

configs/claude/skills/rescue__pull_request_review/SKILL.md · 209 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 104 tokens per session scan A 9ca6a3f26d5a

Subscribe to this mod's changes

rescue__pull_request_review is a skill published in the GitHub repository shunsock/dotfiles (10 stars, last pushed 26d ago), with no licence file. It adds 104 tokens to every session and 2,339 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

github-pr-create

Create a pull request with an auto-generated description. Use when the user asks to open a PR for the current branch's changes.

aiya000/dotfiles · 30 tokens

apply-pr-review

A pull-request review workflow for GitHub. A pull request is a proposed code change, and review conversations are the comments and discussions attached to it.

aiya000/dotfiles · 70 tokens

verify-behavior

Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…

nicknisi/dotfiles · 68 tokens

source-drafting

Use when drafting documents, reports, posts, presentations, or review comments from source materials, or conducting research across provided documents. Enforces read-first drafting, a source map for every claim, agent verification, and separation of verified from unverified claims.

nicknisi/dotfiles · 54 tokens

write-tech-note

Write a Japanese technical article for Zenn or Qiita in aiya000's own writing style, learned from his past articles, with the target platform decided from the current directory. Use when the user asks to write, draft, or rewrite a tech article, blog post, or note, or invokes /write-tech-note.

aiya000/dotfiles · 69 tokens

show-issues-overview

Show a table-formatted overview of the current repository's issues, from GitHub Issues, GitLab Issues, or a TODO.md-like file when the project has neither. Use when the user asks what issues/tasks are open, wants to decide what to work on next, or invokes /show-issues-overview.

aiya000/dotfiles · 69 tokens