lint-kb

To check knowledge base documentation completeness, validate the presence of required ticket files like 1-definition.md, 2-plan.md, 3-spec.md, 4-progress.md, and 5-final.md. This process identifies documentation gaps and enforces formatting standards across uncommitted changes and recent commits.

The best way to enforce KB formatting standards is by running a documentation linter over your knowledge base directory. It enforces documented formatting rules, checks index integrity, validates roadmap references, and generates clear reports with auto-fix suggestions for common issues.

You can validate index integrity and roadmap references by running a KB linting check across your knowledge base artifacts. This ensures alignment and traceability within your documentation by verifying that index files and roadmap references remain consistent and correctly linked.

Yes, you can lint KB documentation across uncommitted changes, recent commits, and full-ticket checks. The linter evaluates your knowledge base directory to identify documentation gaps and enforce formatting standards regardless of the commit stage of your files.

Yes, the KB documentation linter provides auto-fix suggestions for common formatting issues. It generates clear, actionable reports that identify documentation gaps and offer guidance to improve and maintain knowledge base quality across your tickets.