review-comments

To clean up stale comments and docstrings after refactoring, you can audit specified directories to identify outdated comments, commented-out code, and misleading documentation, then review findings before edits are applied.

The best way to remove commented-out code is to run an automated audit across your directories that flags dead code blocks for approval before deletion, ensuring no necessary logic is lost.

Yes, you can enforce custom style references for comment density and formatting by supplying specific guidelines, which the audit uses to evaluate and standardize comments and docstrings across your files.

Yes, the comment review process requires manual approval before editing files, presenting all identified issues like misleading docstrings and dead code for your review to ensure accurate modifications.

To ensure docstrings accurately reflect function behavior, scan your codebase to detect misaligned docstrings, verifying that the documentation matches the actual implementation before applying updates.