A high-effort workflow for reviewing the current GitHub pull request, fixing failed checks, and preparing it for a verified squash merge. A pull request is a proposed code change submitted for review before it is merged.

Use it to run a complete review-and-fix cycle, ready a pull request, squash-merge it through GitHub’s REST API, and confirm that the merge succeeded.

It gathers review and check results, repairs problems, and verifies the exact change that gets merged instead of relying on an unchecked approval.

cr — Skill for Claude Code and Codex by julien777z: A high-effort workflow for reviewing the current GitHub pull…

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.

agentmods

npx agentmods add skills/julien777z/code-review-action/cr

Any agent

npx skills add julien777z/code-review-action --skill cr

Clone the repo

git clone --depth 1 https://github.com/julien777z/code-review-action

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/julien777z/code-review-action/cr.svg)](https://agentmods.dev/skills/julien777z/code-review-action/cr)

Your own site

<a href="https://agentmods.dev/skills/julien777z/code-review-action/cr"><img src="https://agentmods.dev/badge/skills/julien777z/code-review-action/cr.svg" alt="Measured on agentmods" 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 2,386 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 100% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00040	$0.02386
Opus 5	$0.00020	$0.01193
Sonnet 5	$0.00008	$0.00477
Haiku 4.5	$0.00004	$0.00239

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

Security

Grade A, and why

cr 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 5d 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

This is a copy

100% identical to cr — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/cr/SKILL.md · 73 lines

How it starts

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

CR

Run the complete high-effort fix review before merging the current branch's pull request.

Dependencies

code-review — run the complete review and fix workflow before the merge gate.

GitHub Transport

Use GitHub's REST API through gh api by default. Never call a gh subcommand that uses GraphQL, including gh pr, gh repo, and gh search.

Use REST endpoints for every pull-request operation:

Find or inspect a PR: GET /repos/{owner}/{repo}/pulls, GET /repos/{owner}/{repo}/pulls/{number}, and GET /repos/{owner}/{repo}/pulls/{number}/commits.
Create a ready-for-review PR: POST /repos/{owner}/{repo}/pulls with title, head, base, body, and draft=false.
Inspect checks and reviews: GET /repos/{owner}/{repo}/commits/{sha}/check-runs, GET /repos/{owner}/{repo}/commits/{sha}/status, and the pull-request review endpoints.
Squash merge: PUT /repos/{owner}/{repo}/pulls/{number}/merge with merge_method=squash and sha equal to the exact gated head.
Verify the result: re-read GET /repos/{owner}/{repo}/pulls/{number} and require merged=true.

Never create a draft pull request. An existing draft pull request remains reviewable: complete the review and fix cycle without waiting for it to become ready. Before the final check-and-merge gate, make the pull request ready through REST when possible; use markPullRequestReadyForReview through gh api graphql only after REST cannot perform that transition. Obtain node IDs through REST, re-read the result through REST, and return to REST for every subsequent operation. Report the failed REST response before using the fallback. Do not use GraphQL for reads, checks, reviews, merging, or verification when their REST endpoints work. If a REST or required GraphQL request is rate-limited, report the response, wait until the documented reset through the host's event or wait mechanism, and retry the same transport. Treat the rate limit as a blocker only when the host cannot wait for the reset or the reset does not restore access; never switch transports to evade it.

Read the full file on GitHub · 73 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.

5d ago First seen · 73 lines · 40 tokens per session scan A b264ae46966d

Subscribe to this mod's changes

cr is a skill published in the GitHub repository julien777z/code-review-action (2 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 2,386 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cr, differing in 0 lines, and is treated as a copy.

Code review Git and workflow

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens