speckit-review-comments

To detect comment rot, you verify factual accuracy and completeness of code comments against actual implementation behavior. This process flags misleading statements, obsolete logic references, and missing assumptions to prevent outdated documentation from accumulating.

The best way to review code comments for technical debt is evaluating each comment against real code behavior, edge cases, and misinterpretation risks. This identifies misleading documentation and provides targeted rewrite guidance for necessary changes.

You check if code comments match implementation behavior by assessing documentation completeness against actual code execution. This verifies claims, checks for missing error conditions or side effects, and flags ambiguous statements that no longer reflect the code.

Yes, spec-kit comment review works with recently changed files by using deterministic changed-file detection. It analyzes comments within modified files to ensure accurate documentation tracks evolving code without reviewing the entire repository.

You should not use automated comment accuracy checks when no deterministic changed-file detection mechanism is available. The review process requires identifying specific modified files to evaluate comments against real code behavior and edge cases.

You assess documentation completeness by checking each comment for missing assumptions, side effects, error conditions, and rationale. The review provides structured feedback covering critical issues, improvement opportunities, and recommended removals.