From aidoc-flow
Reviews documentation for data inconsistencies, broken references, typos, and unclear terminology. Use before publishing or committing to catch cross-file quality issues.
How this skill is triggered — by the user, by Claude, or both
Slash command
/aidoc-flow:doc-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A cross-cutting documentation quality reviewer. `doc-review` analyzes one file
A cross-cutting documentation quality reviewer. doc-review analyzes one file
or an entire folder for four classes of issue — data inconsistencies,
reference errors, typos/formatting, and terminology — and reports
findings by severity. It is content/quality focused; it does not enforce SDD
structure or traceability.
Layer: cross-cutting utility (produces no artifacts).
Use to review documentation before publication or commit, after a batch of generation, or to audit a folder for cross-file consistency.
Do NOT use for:
../trace-check/SKILL.md;../doc-validator/SKILL.md;../doc-<layer>-audit/SKILL.md.| Mode | Input | Behavior |
|---|---|---|
| Single file | a file path | Deep analysis of one file |
| Folder | a directory path | Analyzes all files together, adding cross-file checks (terminology consistency, cross-document references, duplicate content) |
Optional inputs: scope (quick / full / deep), focus
(data,references,typos,terms), report_format (markdown / json /
summary).
The skill discovers the target files, then runs four reviewers in parallel and merges their findings:
last_updated >= created), version format,
duplicate content. Codes DATA-*.@brd:/@prd:/@ears:/@bdd:/
@adr:/@spec:/@tdd:/@iplan:), circular references. Codes REF-*.TYPO-*.TERM-*.Findings are ERROR (must fix), WARNING (should fix), or INFO. Default
gate: 0 errors; warnings allowed by scope (quick ≤10, full ≤5,
deep 0). Auto-fix (opt-in) is limited to simple, safe patterns — date/count
normalization, relative-path fixes, tag-format fixes, doubled words,
punctuation/whitespace. Everything else is reported for manual review.
A project may add a custom dictionary and severity overrides (e.g. a
.doc-review.yaml) to suppress domain-term false positives.
../doc-validator/SKILL.md../trace-check/SKILL.md../doc-naming/SKILL.md../quality-advisor/SKILL.md../doc-flow/SKILL.mdframework/governance/DOC_GOVERNANCE_CORE.md../charts-flow/SKILL.mdnpx claudepluginhub vladm3105/aidoc-flow-framework --plugin aidoc-flowValidates project documentation: lints formatting and naming, checks broken/orphan links, verifies glossary terms and synonyms, detects contradictions/gaps, audits completeness via /doc:lint, /doc:links, etc.
Reviews end-user and product documentation for voice/tone, structure, completeness, clarity, and technical accuracy. Flags issues with prioritized findings and pass/needs-revision verdict.
Assesses documentation quality across readability, consistency, audience fit, and prose clarity. Produces a scored review with actionable findings. Use before releases, during doc reviews, or when docs feel unclear.