de-slop

To remove AI-generated artifacts before a git commit, run a dry-run scan to identify redundant comments, AI TODOs, and excessive docstrings, then use numbered selections to safely edit your changed files while preserving formatting.

You can clean up excessive docstrings and stray markdown notes by scanning your changed Git files to flag unnecessary AI artifacts, offering numbered selections to optionally delete them while keeping essential documentation intact.

No, the dry-run scan safely previews AI artifacts and unnecessary code in your changed files without modifying them, providing numbered selections so you can manually approve edits before finalizing your local commits or PR preparation.

The code cleanup process avoids touching test files unless explicitly selected, ensuring your test suite remains unaffected while scanning changed Git files for redundant comments and unnecessary markdown notes during local commit preparation.

No, you do not need GitHub to scan changed files for unnecessary markdown notes and AI TODOs; the workflow is Git-only and operates entirely on local changes during commit and PR preparation.

The best way to prepare clean commits is to perform a dry-run scan on your Git changed files to identify and remove AI noise like redundant comments and stray markdown notes, preserving formatting through safe numbered edit selections.