reslop

To rewrite inaccurate docstrings, the tool reads implementations, greps call sites, and checks adjacent tests to replace overhyped descriptions with factual, code-grounded statements. It produces safe old-to-new diffs without inventing behavior or performance metrics.

Codebase alignment for repo hygiene replaces hallucinated or repetitive comments with short, factual descriptions grounded in the repository's actual implementation. It targets specific file scopes or pending-change files to avoid touching unrelated code.

Yes, you can clean up slop docstrings in pending changes by providing a targeted scope or asking to rewrite within your modifications. This confines edits to specified paths or pending-change files, preventing unrelated repository files from being touched.

Docstring rewriting removes unsupported quantitative claims and hate-words by applying guardrails that prevent reintroducing slop. It blocks unsupported performance or numeric assertions unless explicitly grounded by injected context from tests or implementation.

The best way to generate safe diffs for comment rewriting is a diff-first workflow that groups old-to-new changes by file. It requires consulting implementation and test invariants before proposing replacements, letting you apply selected or all changes safely.

You should not use automated docstring cleanup when your repository lacks sufficient test coverage or call sites to verify invariants. The tool avoids inventing behavior or performance metrics and requires grounding in actual implementation to produce safe replacements.