comment-quality

To fix temporal language in code comments, scan targeted files or directories to detect temporal, development-activity, and relative wording. The process produces a structured findings report with file paths, line numbers, and precise timeless rewrites describing what the code does and why.

Temporal words like new, old, or now hurt maintainability because they become stale as projects evolve. Rewriting them into timeless comments that explain current behavior and rationale ensures documentation remains accurate and clear for future code reviews.

Provide a file path or set of files to scan. The scanner analyzes comments across common languages, identifies temporal and relative wording, and returns a structured report containing file paths, line numbers, current text, and suggested timeless replacements.

Yes, the comment rewriting tool works across common programming languages. It scans comments regardless of language to identify temporal and development-activity terms, generating precise rewrites and a structured findings report suitable for pre-release audits.

The best way to prepare comments for a pre-release audit is scanning the codebase to identify temporal language. This generates a structured report with exact line numbers and replacement suggestions that describe what the code does, ensuring documentation is timeless and clear.