pr-recheck

pr-recheck is a skill for Claude Code from yuri-semenenko/ai-engineering-workspace. It costs 76 tokens per session (2,171 once invoked), scanned A, original, MIT.

A second review of a pull request after the author has responded to earlier review comments and pushed new commits. It checks each still-open discussion against the updated code.

In plain words
What is it for?
Use it to inspect new commits, classify prior comments as addressed, partial, or unresolved, resolve completed discussions, and approve or add further inline comments when appropriate.
Why use it?
It prevents addressed issues from being raised again and highlights comments that were only partly or not at all fixed. A pull request is a proposed code change submitted for review before merging.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents.

Good fit Use it to inspect new commits, classify prior comments as addressed, partial, or unresolved, resolve completed discussions, and approve or add further inline comments when appropriate.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yuri-semenenko/ai-engineering-workspace/pr-recheck
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 yuri-semenenko/ai-engineering-workspace --skill pr-recheck
Clone the repo
git clone --depth 1 https://github.com/yuri-semenenko/ai-engineering-workspace

Made for: Claude Code.

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 pr-recheck

README.md
[![agentmods](https://agentmods.dev/badge/skills/yuri-semenenko/ai-engineering-workspace/pr-recheck/github.svg)](https://agentmods.dev/skills/yuri-semenenko/ai-engineering-workspace/pr-recheck)
Your own site
<a href="https://agentmods.dev/skills/yuri-semenenko/ai-engineering-workspace/pr-recheck"><img src="https://agentmods.dev/badge/skills/yuri-semenenko/ai-engineering-workspace/pr-recheck/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 pr-recheck

Your own site · 80×15
<a href="https://agentmods.dev/skills/yuri-semenenko/ai-engineering-workspace/pr-recheck"><img src="https://agentmods.dev/badge/skills/yuri-semenenko/ai-engineering-workspace/pr-recheck.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,171 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.00076 $0.02171
Opus 5.5 $0.00030 $0.00868
Sonnet 5.5 $0.00015 $0.00434
Haiku 4.5 $0.00008 $0.00217

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

Security

Grade A, and why

pr-recheck 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 2d 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.

claude-code/.claude/skills/pr-recheck/SKILL.md · 143 lines

How it starts

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

PR recheck

Follow-up pass on a PR that has already been reviewed once. Assumes a prior round of inline comments exists and the author has pushed fixes since.

Preconditions

The same checks as pr-review: run gh auth status; require a PR number/URL or a checked-out branch with an open PR; verify open state via gh pr view <id> --json state,mergedAt. One difference: if it is merged or closed, surface that and stop rather than asking, because there is no thread left to resolve and nothing to approve.

Steps

  1. Load prior threads. Fetch open review threads via GraphQL — REST does not expose thread resolution state:
    gh api graphql -f query='query($owner:String!,$repo:String!,$num:Int!,$cursor:String){
      repository(owner:$owner,name:$repo){ pullRequest(number:$num){
        reviewThreads(first:100,after:$cursor){ pageInfo{hasNextPage endCursor} nodes{ id isResolved
          comments(first:20){ pageInfo{hasNextPage endCursor} nodes{ path line body author{login} } } } } } } }' \
      -f owner=OWNER -f repo=REPO -F num=N
    
    Page reviewThreads until hasNextPage is false, passing each endCursor as cursor. For every open thread, page its comments connection via node(id: $threadId) { ... on PullRequestReviewThread { comments(first: 100, after: $cursor) { pageInfo { hasNextPage endCursor } nodes { body author { login } } } } } until complete. Retain the first comment author and the authenticated user's replies with bodies, including replies after the first page. If any page is unavailable or incomplete, report that evidence gap; do not infer that the user did not accept a risk or mark it accepted without evidence. Keep only threads with isResolved: false.
  2. Load new work. Diff and commits since the previous review (gh pr diff <id> plus the commit log). Read the new code fully, cross-referencing touched files.
  3. Build the verification matrix. For each open thread, record three separate things, with the file:line and the commit that addresses it. Output as a table.
    • Severity, from the first review: Critical / Important / Optional. When the thread does not state it, classify it from what it describes under pr-review rules and mark the severity as inferred. When it reads as either of two tiers, take the higher one: severity alone decides what blocks, and pr-review posts comments as prose that rarely names a tier.
    • Status: addressed / partial / not addressed / wont-fix (author replied). A wont-fix reply is the author's position, not the reviewer's acceptance. addressed (not resolved) marks an addressed thread another reviewer opened, which the decision gate leaves open for them; it does not block.
    • Blocks approval: yes, no, or no (accepted risk). A Critical or Important thread blocks unless it is addressed or its risk is accepted. An Optional thread does not block.

Read the full file on GitHub · 143 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. 2d ago Changed 2457f9e45cb8
  2. 4d ago Changed · +26 lines 504235ba0829
  3. 14d ago Changed · +38 lines · -33 tokens per session cdb4c0fbdda3
  4. 2mo ago First seen · 79 lines · 109 tokens per session scan A 33ef270c7923

Subscribe to this mod's changes

pr-recheck is a skill published in the GitHub repository yuri-semenenko/ai-engineering-workspace (4 stars, last pushed 4d ago), licensed MIT. It adds 76 tokens to every session and 2,171 once invoked, about $0.0003 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

pr-recheck compared with skills from other repositories

pr-recheck next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
pr-recheckyuri-semenenko/ai-engineering-workspaceSkill44d agoMITA76Claude Code
056-design-avoid-breaking-changesjabrena/plinthSkill4623d agoApache-2.0A106Claude Code, Codex
shiprjmurillo/ai-agentsSkill49todayMITA80Claude Code
git-advanced-workflowsrjmurillo/ai-agentsSkill49todayMITA90Claude Code
ai-prarcasilesgroup/ai-engineeringSkill655d agoApache-2.0A60Claude Code, Codex
maintainer-reviewrjmurillo/ai-agentsSkill49todayMITA73Claude Code
chestertons-fencerjmurillo/ai-agentsSkill49todayMITA80Claude Code