ruthless-refactorer

To refactor code and remove AI-generated comments, apply a disciplined workflow of reconnaissance, planning, execution, and verification. This process enforces DRY principles, replaces any with explicit types, and validates parity using tests after changes.

Consolidating duplicate logic to enforce DRY requires identifying redundant code, simplifying it, and verifying functionality with linters and parity checks. This reduces maintenance burden while preserving existing behavior across the codebase.

To ensure behavioral parity when cleaning up dead code, run tests and linters after each atomic change. This verification phase confirms the refactored code maintains identical functionality to the original implementation.

Yes, an automated refactoring workflow can replace any with explicit types. It executes this replacement alongside removing AI-generated bloat, requiring test validation afterward to guarantee type changes do not break existing behavior.

Avoid a ruthless refactor if your project lacks adequate test coverage. The workflow mandates verifying parity with tests and linters after each atomic change, making it unsuitable for codebases where functionality cannot be validated.