Harness Docs Pipeline

To detect documentation drift across your codebase, you can run an automated docs pipeline health check. This orchestrates sub-skills to identify outdated context, missing AGENTS.md files, and broken links, applying both graph-backed analysis and static fallbacks.

A documentation gap audit identifies missing coverage and outdated context within a project. It works by orchestrating detection sub-skills that analyze your codebase structure to find missing AGENTS.md files and broken links, generating a comprehensive health report.

Yes, you can automatically regenerate AGENTS.md files for existing projects. By running the documentation pipeline with the appropriate options, the tool orchestrates alignment and validation sub-skills to freshen outdated context and remediate detected documentation gaps.

You can run documentation health checks in a CI pipeline by utilizing the --ci option. This orchestrates drift detection, gap auditing, and link validation across your codebase, failing the pipeline if broken links or outdated context are detected.

The best way to fix broken links and outdated context is to run an automated docs pipeline with the --fix option. This orchestrates remediation sub-skills to align documentation, validate context engineering, and regenerate missing AGENTS.md files.

No, you do not need a knowledge graph to perform documentation drift detection. The pipeline supports graph-backed analysis for comprehensive mapping but includes static fallbacks with bootstrap options to ensure functionality without a graph dependency.