context-maintenance

To audit project documentation for inconsistencies after a large refactor, run a full check across your SPEC.md, API.md, CONTEXT.md, RULES.md, and CHANGELOG.md files. The audit enforces a layered contract by performing existence, structure, and changelog checks to surface drift.

Checking for missing documentation files in your CI/CD pipeline involves verifying the existence and structure of your project's docset. You can run scope-flexible audits from any subdirectory to perform health checks and generate actionable insights for repairing missing files.

Validating changelog and version consistency across multiple project modules requires applying layered checks to your documentation set. The audit performs changelog and version validation to enforce the documentation contract and reports findings for bulk remediation.

Yes, you can run a documentation consistency check from a specific subdirectory rather than the whole project. Scope-flexible audits allow you to start from any subdirectory, enabling targeted doc health checks for multi-module projects and new-team onboarding workflows.

Before running an automated doc audit, you need a five-piece documentation structure consisting of SPEC.md, API.md, CONTEXT.md, RULES.md, and CHANGELOG.md. The audit checks this layered contract to identify missing files, broken links, and outdated entries.

Project documentation drifts during refactoring when code changes are not reflected in the docset. To fix it, an audit performs existence, structure, and changelog checks across SPEC, API, CONTEXT, RULES, and CHANGELOG files, generating actionable insights to guide bulk remediation.