spec-code-review

spec-code-review is a skill for Claude Code from ronronner02/codepilot-agent. It costs 48 tokens per session (27,802 once invoked), scanned A, original, MIT.

A structured code-review workflow for finding bugs, regressions, missing tests, and standards problems. A regression is a new failure caused by a change that previously worked.

In plain words
What is it for?
Reviewing code for defects and test gaps, then applying fixes only when the user explicitly asks for a review and fixes.
Why use it?
It provides consistent review findings while keeping the default behaviour limited to reporting problems.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions CLAUDE.md; mentions subagents; names the AskUserQuestion tool.

Good fit Reviewing code for defects and test gaps, then applying fixes only when the user explicitly asks for a review and fixes.

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/ronronner02/codepilot-agent/spec-code-review"><img src="https://agentmods.dev/badge/skills/ronronner02/codepilot-agent/spec-code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 27,802 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.00048 $0.27802
Opus 5.5 $0.00019 $0.11121
Sonnet 5.5 $0.00010 $0.05560
Haiku 4.5 $0.00005 $0.02780

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

Security

Grade A, and why

spec-code-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.

The scan reads SKILL.md. This mod also ships 5 executable files (scripts/cross-model-adversarial-review.sh, scripts/findings-mechanics.py, scripts/peer-job-runner.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/spec-first/workflows/spec-code-review/SKILL.md · 1,036 lines

How it starts

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

Code Review

Reviews code changes against intent, tests, standards, and risk lenses. When reviewer dispatch is explicitly authorized and callable, it uses selected personas and merges structured findings; otherwise it performs an honest inline report-only review with degraded coverage.

Workflow Contract Summary

  • 输入: 当前分支、显式 base、远端 branch/PR,及可选 plan/task-pack 上下文。
  • 输出: 默认 report-only 的结构化 findings、actionable queue、coverage、验证限制与 run artifact;mode:agent 返回 JSON。
  • 硬出口: scope/base 不可解析、task context 漂移或越界、错误 checkout、必需独立覆盖不可用时不得给出完整 merge-ready 声明。
  • 权威: source/diff/test/log 提供事实,reviewers 判断语义;review、local mutation、commit 与 landing 是四个独立授权面。
  • 消费者: 人工 reviewer、spec-work、caller-owned shipping/LFG 流程与后续 residual gate。

When to Use

  • Before creating a PR
  • After completing a task during iterative implementation
  • When feedback is needed on any code changes
  • Can be invoked standalone
  • Can run inside larger workflows; use mode:agent when the caller needs JSON instead of markdown tables

Scenario Capability

Follows docs/contracts/workflows/scenario-capability-matrix.md. Overrides: high-risk

  • foreign-residual-workspace -> blocked-action-required: stop before reviewer dispatch that depends on suspect local artifacts, checkout mutation, root-cause-like review claims, or PR-ready verdicts until the named cleanup/init action runs or the user explicitly accepts degraded evidence.
  • optional external-tool evidence unavailable -> fallback-only: use bounded direct source, diff, test, log, and user-provided evidence; disclose missing reviewer/tool coverage and do not claim unconfirmed impact or full review coverage.
  • non-git-build-workspace coverage gaps -> partial: review only the selected repo/inspected build surfaces and directly inspect uncovered modules before claiming they are unaffected.

Argument Parsing

Parse the invocation arguments supplied by the current host for optional tokens. Strip only recognized tokens while preserving quoted paths, Windows drive paths, URLs, and the order of the remainder before interpreting it as a PR number, GitHub URL, or branch name.

Read the full file on GitHub · 1,036 lines

Files

What ships with it

31 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 1,036 lines · 48 tokens per session scan A e6d1b0c08bb2

Subscribe to this mod's changes

spec-code-review is a skill published in the GitHub repository ronronner02/codepilot-agent (0 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 27,802 once invoked, about $0.0002 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

trace

Use when encountering bugs, test failures, runtime errors, broken builds, or "this doesn't work" reports. Systematic root-cause analysis before any patch — never blind-patches symptoms. Standalone, ends with a final-integration review of the fix. Trigger with /hyperflow:trace, "debug this", "find the root cause", "why…

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

verification-and-release

Design risk-based verification and judge release readiness from traceable evidence. Use when deciding what must be proven or whether an integrated change can ship.

cmdr-chara/codex-toolkit · 32 tokens

pr-review

Review Cool Workflow pull requests or branch diffs. Use when Codex must inspect code changes for bugs, regressions, FreeBSD/POLA violations, missing tests, generated artifact drift, release-contract risk, or CI implications, and return findings first with file/line citations.

coo1white/cool-workflow · 58 tokens

nazgul:heartbeat

Run one Nazgul automation-heartbeat tick — triages the work inbox and auto-starts the next objective if idle. Opt-in and default-off; fired by an optional Claude Code native scheduled agent (routine) or run by hand. Use when asked to "run a heartbeat tick", "check the inbox", or to test/debug the heartbeat.

OrodruinLabs/nazgul · 74 tokens

code-review

Perform a structured code review of changes, checking for correctness, style, tests, and potential issues.

langchain-ai/deepagents · 23 tokens

code-review

Reviews code for bugs, security issues, and best practices.

promptfoo/promptfoo · 11 tokens