completeness-check

What problem does it solve?

Detects incomplete work left in repositories due to AI assistant crashes, context exhaustion, mid-implementation distractions, or accidental omissions so teams don't mark tasks as finished prematurely.

Core Features & Use Cases

• Broad detection categories: Finds broken internal links, retired file references, hallucinated dependencies, security-critical TODOs, generic TODO/FIXME comments, debug prints, commented-out code, missing tests, placeholder content, stale docs, and orphaned files.
• Phased analysis: Offers fast grep-based scans for quick checks, tool-based analysis (linters, coverage, registry checks) for higher confidence, and deep AST/semantic analysis for expensive investigations.
• Reporting & CI integration: Produces a completeness score, summary or detailed findings, and machine-readable output suitable for pre-commit gates and audit automation.

Quick Start

Run a completeness-check on the repository to surface TODOs, missing tests, hallucinated dependencies, broken links, and receive a completeness score with a verification report.