polish

To remove AI slop and clean lint errors in your git branch, you need a tool that targets changed files in git diff main...HEAD. It strips stray comments and dead code without altering logic, then runs available linters like ESLint or Ruff to fix remaining issues.

The best way to clean up AI-generated code and comments without altering logic is to run a code polish process confined to your git diff. This removes slop and dead code while preserving the original algorithmic structure of JavaScript, TypeScript, or Python files.

Yes, you need standard tooling like ESLint, Black, Ruff, Prettier, or the TypeScript compiler installed in your workspace. The polish process requires these dependencies to be available so it can automatically run them on changed files to fix lint errors and improve consistency.

Yes, you can run code cleanup and linting only on files changed in your current branch. The process confines its operations to files detected by git diff main...HEAD, ensuring safe polish during collaborative development without touching untouched code.

Yes, code polish works with Python, JavaScript, TypeScript, and their related configuration files. It identifies and removes slop, stray comments, and dead code across these languages, then applies appropriate formatters like Black, Ruff, ESLint, or Prettier.

You should not use automated linting on your entire codebase during active development because it can create unsafe modifications outside your current scope. Confining cleanup to git diff main...HEAD ensures safe polish during collaborative development without introducing unexpected changes.