completeness-check

To detect incomplete work before release, scan repositories for broken links, retired references, hallucinated dependencies, debug statements, and TODOs. This process produces a completeness score and verification report to prevent prematurely marking tasks as finished.

A completeness check identifies accumulated technical debt from mid-implementation distractions or AI assistant crashes. Run it during pre-commit gates and CI checks to catch missing tests, placeholder content, and orphaned files before merging code.

Yes, a completeness audit finds hallucinated dependencies, broken internal links, and retired file references. It applies broad detection categories using grep-based scans, linters, and deep AST analysis to verify repository integrity.

Automate code quality coverage checks by running tool-based analysis alongside fast grep scans. This surfaces security-critical TODOs, stale docs, and commented-out code, generating machine-readable output suitable for audit automation.

Completeness checking integrates with existing workflows by offering tool-based analysis using linters, coverage reports, and registry checks. This provides higher confidence verification alongside standard CI automation processes.

Standard pre-commit checks often miss orphaned files and commented-out code because they lack deep AST analysis. A dedicated completeness scan applies semantic investigations to catch these specific mid-implementation distractions.