documentation-sync

Documentation drift detection compares API signatures, configurations, and embedded examples against your codebase using static analysis and AST extraction to identify mismatches before release or during pull requests, flagging what needs updating in a drift report.

Example validation executes embedded code snippets from your documentation to verify they run correctly and produce expected output, catching broken examples before they confuse users or during onboarding.

Auto-update functionality regenerates architecture diagrams and refreshes API documentation in READMEs based on current code signatures and configurations, running automatically during releases and refactoring to eliminate manual sync work.

Static code analysis and AST-based signature extraction parse your codebase to automatically extract current API definitions, configurations, and structure, creating a source of truth that documentation validation and updates reference.

Documentation sync runs as a check during pull requests to catch drift before merge and executes before releases to validate that all code examples, signatures, and diagrams match the current codebase, preventing inconsistent deployments.

Diagram generation creates architecture diagrams from code analysis, so you don't need pre-existing diagrams; the Skill produces diagram code you can version alongside your documentation.