Detect and report drift between markdown documentation and source code.
npx skills add https://github.com/cmbays/mokumo --skill doc-sync-cmbays
Please help me install this Agent Skill. Skill: doc-sync Source: https://github.com/cmbays/mokumo/tree/main/.claude/skills/doc-sync Command: npx skills add https://github.com/cmbays/mokumo --skill doc-sync-cmbays
This Skill ensures that your project documentation accurately reflects the current state of your codebase, preventing outdated information and maintaining a reliable source of truth.
APP_FLOW.md and PRD.md still accurately describe the new routes and their functionality.Run the doc-sync skill to audit all canonical documentation against the current codebase.
High-intent search queries and answers about installing and using this skill.
To sync project documentation, run an audit that compares markdown files against source code, package manifests, and application routes. The process detects discrepancies across technical specifications and API documentation, generating a report that details the drift and suggests fixes.
Documentation drift detection is the process of comparing project plans and technical specifications against the actual codebase to find outdated information. You need it after updating API endpoints or application routes to ensure your markdown files remain a reliable source of truth.
Yes, you can automatically check API documentation accuracy by comparing markdown files against source code and application routes. This generates a clear report detailing any detected drift and suggesting fixes to keep your technical specifications aligned with the codebase.
Yes, doc-sync works with markdown files and package manifests by comparing them directly against the codebase. It validates project plans, technical specifications, and API documentation by checking application routes and source code to identify discrepancies.
The best way to keep technical specifications in sync is to run drift detection that compares markdown files against source code, package manifests, and application routes. This generates a report detailing discrepancies and suggesting fixes to maintain accuracy across project documentation.
arielybarakCompare codebase state against spec-kit plans and append missing tasks to tasks.md.
OdradekAIUpdate and synchronize opi documentation with English and Chinese mirrors.
0x0pointerAnalyze source code for security issues using the ASVS 5.0 framework.
Asharf30Cross-reference documentation claims against source code implementations.