A code-review checklist and process for checking changes before they are finished. It covers correctness, completeness, tests, code quality, and documentation.

Use it after implementing a feature, bug fix, or other code change to inspect the differences, run relevant checks, and decide whether the work is ready.

It provides a separate review of completed work so logic errors, missing tests, unfinished tasks, or unclear code are less likely to remain unnoticed.

review — Skill for Claude Code by tessro/fab

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 tessro/fab --skill review

Clone the repo

git clone --depth 1 https://github.com/tessro/fab

Made for: Claude Code.

Or install fab, the plugin that ships this one along with the rest of its 2 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tessro/fab/review/github.svg)](https://agentmods.dev/skills/tessro/fab/review)

Your own site

<a href="https://agentmods.dev/skills/tessro/fab/review"><img src="https://agentmods.dev/badge/skills/tessro/fab/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tessro/fab/review"><img src="https://agentmods.dev/badge/skills/tessro/fab/review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 607 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.

Model	Per session	Once invoked
Fable 5.1	$0.00034	$0.00607
Opus 5.5	$0.00014	$0.00243
Sonnet 5.5	$0.00007	$0.00121
Haiku 4.5	$0.00003	$0.00061

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

Security

Grade A, and why

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 2mo 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.

internal/plugin/files/skills/review/SKILL.md · 66 lines

How it starts

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

Code Review

Perform a thorough code review of your changes before marking your task as complete.

When to Use

Run /review after you have finished implementing a feature, bug fix, or any code changes, but BEFORE running fab issue close or fab agent done.

How to Review

Use the Task tool to spawn a sub-agent for code review. This provides a fresh perspective without the context of how the code was written, leading to more objective reviews.

Step 1: Run the Sub-Agent Review

Use the Task tool with subagent_type: "general-purpose" and a prompt like:

Review all code changes (committed and uncommitted) between main and the current worktree. Run `git diff main` to see all changes.

Check each of these areas:

1. **Correctness**: Does the code solve the problem? Are there logic errors or unhandled edge cases?
2. **Completeness**: Is the implementation fully complete? Any TODOs left behind?
3. **Testing**: Are there tests for new functionality? Do existing tests pass?
4. **Code Quality**: Is the code readable and well-organized? Does it follow project conventions?
5. **Documentation**: Are public APIs documented? Do complex algorithms have comments?
6. **Security**: Any potential vulnerabilities (injection, XSS, etc.)? Is user input validated?
7. **Performance**: Any obvious performance issues (N+1 queries, unnecessary loops)?

Run the test suite and any linters configured for the project.

Report:
- Issues found (with file paths and line numbers)
- Suggestions for improvement
- Confidence level that the implementation is complete and correct

Step 2: Address Feedback

CRITICAL: You MUST address all issues found during review before proceeding. Do not skip, defer, or ignore feedback. The review exists to catch problems - ignoring it defeats the purpose.

After the sub-agent completes its review:

Carefully read through ALL issues and suggestions reported
Fix every problem identified - no exceptions
If the sub-agent raised concerns, address each one explicitly
If significant changes were made, run /review again to verify fixes

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

2mo ago First seen · 66 lines · 34 tokens per session scan A 6fe593195e3c

Subscribe to this mod's changes

review is a skill published in the GitHub repository tessro/fab (24 stars, last pushed 9mo ago), licensed MIT. It adds 34 tokens to every session and 607 once invoked, about $0.0001 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-30.

Code review

review next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
reviewtessro/fab	Skill	24	9mo ago	MIT	A	34	Claude Code
autoreviewopenclaw/clawhub	Skill	9.5k	today	MIT	A	17	Claude Code, Codex
agent-teams-simplify-and-hardenLeoYeAI/openclaw-master-skills	Skill	2.2k	4d ago	MIT	A	115	Claude Code, Codex
omh-code-reviewrlaope/oh-my-hermes	Skill	5.3k	today	MIT	A	49	Claude Code, Codex
revdiff-planumputun/revdiff	Skill	949	today	MIT	A	84	Claude Code
explore-unknownsdzhng/skills	Skill	1.5k	yesterday	MIT	A	162	Claude Code, Codex
re0-mergeLilMGenius/paperthin	Skill	1.4k	today	MIT	A	51	Claude Code, Codex