Use when auditing repository documentation for drift, stale statements, broken references, or README mismatches, especially across published docs under `doc/` and key entry surfaces such as `README.md`, `README-EN.md`, `README-ZH.md`, and `mcp/README.md` during periodic maintenance or before preparing corrective PRs.
SkillScore86Maintained
Automatic
◆Doc Ops pack
Last verified 8/2/2026
What it changes
Passed 17 of 20 test cases with the skill, and 7 of 20 without it.
Without skill36%
With skill86%
Checks it passed that the model alone missed
Read references/review-scope.md first
Route the repair work to pr-review-fix
Prepare targeted documentation updates for a focused PR
and 8 more in the full report
11 fixed8 passed either way3 still failing0 broke
Pass-rate lift
+50 pp
Tokens
-20%
Agent turns
0%
Response time
-66%
Model gemini-3.6-flashMeasured 8/2/2026v219 of 22 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 11
Prompt
In Phase 1 of a documentation freshness audit, what two groups make up the audit surface?
What was checked, without and with the skill
Checked
Without skill
With skill
Group published documentation under doc/ and README surfaces separately
Missed
Passed
case-12 · gemini-3.6-flash · 8/2/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md87 lines3 files
Documentation Freshness Review
Review whether repository documentation still matches the current code, generated assets, and published entry points.
When to use this skill
Use this skill when you need to:
Audit published documentation under doc/ for stale or wrong statements
Check whether README.md, README.zh-CN.md, mcp/README.md, or mcp/README.zh-CN.md drifted away from current behavior
Verify that linked scripts, files, commands, and workflows still exist and still match the repo
Run a periodic docs health check before opening corrective PRs
Separate mechanical doc drift from product ambiguity that still needs human confirmation
Do NOT use for:
Marketing copy polish without a freshness or correctness question
API contract review that depends on CloudBase control-plane docs first
Feature planning or architecture design
Rewriting large docs from scratch when the main need is a targeted drift audit
Workflow
Phase 1 — Scope the surfaces
Read references/review-scope.md first.
Build the audit surface in two groups:
published documentation under doc/
README surfaces such as README.md, README.zh-CN.md, and mcp/README.md
Note which code, scripts, generated files, or workflows those docs claim to describe.
Phase 2 — Evidence-based comparison
Verify whether referenced files, scripts, commands, and workflow names still exist.
Compare the docs against the current implementation, generated outputs, and source-of-truth files.