af-quality-process

To validate documentation quality before committing, you can run an automated quality process that checks frontmatter compliance, link integrity, and content freshness on recently modified files to prevent introducing issues.

Documentation freshness auditing detects stale docs by using git-aware incremental checks to verify that content remains accurate and up-to-date, ensuring knowledge accessibility and reducing errors across the project.

Yes, you can run git-aware incremental quality checks to efficiently validate only recent documentation changes, or you can perform a comprehensive full audit to review the entire documentation set.

The best way to detect and repair stale documentation is using an automated validation workflow that identifies outdated content through freshness checks and triggers repair workflows to restore compliance.

Yes, the documentation quality process extends beyond text validation to also cover code quality and architecture quality, ensuring comprehensive standards are met across the entire project.

Run a full documentation audit when you need a comprehensive review of the entire documentation set for compliance, and use incremental checks for routine validation of recent changes before delivery.