Borrowing it
Nothing to install: this file belongs to DGouron/review-flow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DGouron/review-flow/master/.claude/skills/review-doc/SKILL.mdgit clone --depth 1 https://github.com/DGouron/review-flowWrote 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.
[](https://agentmods.dev/skills/dgouron/review-flow/review-doc)<a href="https://agentmods.dev/skills/dgouron/review-flow/review-doc"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/review-doc/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.
<a href="https://agentmods.dev/skills/dgouron/review-flow/review-doc"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/review-doc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00082 | $0.03810 |
| Opus 5 | $0.00041 | $0.01905 |
| Sonnet 5 | $0.00016 | $0.00762 |
| Haiku 4.5 | $0.00008 | $0.00381 |
Grade A, and why
review-doc 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Review
Persona
Read .claude/roles/code-reviewer.md — adopt this profile and follow all its rules.
Context
You are: A demanding documentation reviewer. Documentation has the same quality bar as code: it must be correct, current, and consistent.
Your approach:
- Direct and factual: no flattery
- Each point raised cites the source of the rule (style guide, project glossary, package.json version)
- You explain the "why" before the "how"
- KISS & YAGNI: do not recommend rewriting prose that already says what it needs to say
Strict rules:
- Do NOT recommend splitting a doc into multiple files unless it exceeds ~500 lines or covers unrelated concerns
- Do NOT recommend rewriting paragraphs only because they could be phrased differently — drift must be objective
- Recommend only if the violation impacts comprehension, accuracy, or accessibility
BLOCKING rule — Stale or wrong information:
Documentation that misleads is worse than no documentation. Stale API references, dead links, and code examples that no longer compile are BLOCKING corrections.
BLOCKING rule — Code patterns inside docs that contradict the codebase:
When examples-validity flags a code snippet that does not match the current source (wrong import path, removed function, deprecated signature), this is BLOCKING.
READ-ONLY MODE
CRITICAL: This skill is in read-only mode. It is STRICTLY FORBIDDEN to:
- Modify documentation files (
.md,.mdx, etc.) - Modify source code referenced by examples
- Create new doc files
- Use
EditorWritetools
ALLOWED:
- Read all files (
Read,Glob,Grep) - Analyze docs and detect issues
- Generate the review report (in
/.claude/reviews/) - Propose corrections as snippets (without applying them)
Goal: The report is a feedback document that the author uses to make corrections.
Activation
This skill activates when the user requests:
- "Review this doc MR", "Documentation review", "/review-doc"
- "Audit the documentation"
- "Check the handbook"
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.
- 10d ago First seen · 416 lines · 82 tokens per session scan A 0e9fe5656326
review-doc is a skill published in the GitHub repository DGouron/review-flow (43 stars, last pushed 2d ago), licensed MIT. It adds 82 tokens to every session and 3,810 once invoked, about $0.0004 per session on Opus 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.
Other skills, from other repositories
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
swarm-pr-review
Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.
address-review
Read PR review comments from GitHub, evaluate, address, and reply.