code-cleanup

To safely clean up TypeScript and JavaScript, provide the exact file or module to target. The workflow applies a single, behavior-preserving cleanup pass that removes dead code and simplifies type-level indirection while verifying changes against tests.

Behavior-preserving code cleanup reduces complexity by removing dead code, simplifying types, and inlining private helpers without changing functionality. You need it when your Rust, TypeScript, or JavaScript codebase must align with project guidelines while guaranteeing existing behaviors remain intact.

No, this workflow performs focused cleanup on targeted scopes within a repository, not the entire codebase at once. You provide the exact file or module to clean, ensuring a strict, high-value single pass that preserves behavior safely.

The best way to simplify type-level indirection is a strict workflow with critique, a single cleanup pass, and closure verification. This process validates changes against repository guidelines and tests to prevent unintended behavior changes in Rust, TypeScript, and JavaScript.

Unlike automated formatting tools, a focused refactor workflow enforces critique and closure verification to remove dead code and inline private helpers safely. It ensures behavior preservation by validating changes against repository guidelines and tests, not just syntax styling.