Compare code behavior against documentation and generate a severity-tagged drift report.
npx skills add https://github.com/benkruger/flow --skill flow-doc-sync
Please help me install this Agent Skill. Skill: flow-doc-sync Source: https://github.com/benkruger/flow/tree/main/skills/flow-doc-sync Command: npx skills add https://github.com/benkruger/flow --skill flow-doc-sync
Full codebase documentation accuracy review. Compares behavioral sources (skills, lib scripts, config files) against all documentation surfaces (README.md, docs/**/.md, CLAUDE.md, .claude/rules/.md) and produces a severity-tagged drift report. Read-only — reports drift but does not fix anything.
Run the flow-doc-sync skill to generate a drift report comparing code behavior with documentation.
High-intent search queries and answers about installing and using this skill.
Documentation drift is detected by comparing behavioral sources like scripts and config files against all documentation surfaces, generating a severity-tagged report that identifies mismatches without modifying code.
Checking for stale documentation involves scanning all markdown surfaces including README.md and docs directories, then comparing them against actual code behavior to produce an actionable drift report with severity tags.
Yes, you can audit documentation accuracy in read-only mode, which reports drift findings like STALE, MISSING, and OUTDATED entries without altering any code or documentation files.
To generate a drift report, the tool scans behavioral sources and compares them against documentation surfaces including CLAUDE.md and .claude/rules directories, outputting inline findings and a completion banner.
A documentation drift report includes severity-tagged findings categorized as STALE, MISSING, or OUTDATED, highlighting specific mismatches between documented behavior and actual code implementation.
Yes, documentation drift detection scans all markdown surfaces including nested paths like docs/**/*.md, ensuring comprehensive coverage across the entire codebase documentation structure.
Asharf30Cross-reference documentation claims against source code implementations.
BoardPandasCross-references documentation files against public APIs, endpoints, and configuration options to generate an issue report.
fall-out-bugAnalyze codebases to validate architecture and documentation alignment.
umairinayatLint, format, and statically analyze Node.js and Python code changes.
