pruner

To remove dead code during a code review, surface deletion candidates and propose inline replacements for premature abstractions. This simplifies code changes by identifying unreachable branches and redundant checks without altering functionality.

Code simplification through pruning is the process of identifying and removing premature abstractions, dead code, and redundant validation. It reduces complexity while validating that behavior remains unchanged with respect to tests and contracts.

Find unreachable branches and stale leftovers by scanning for deletion candidates during post-merge cleanup. The process detects dead code and flags defensive checks on impossible states to improve maintainability.

Yes, you can simplify code across languages commonly used in software projects. The pruning mechanism applies broadly to surface removals and simplifications that preserve behavior regardless of the specific language.

Code cleanup does not affect existing contracts and tests. The pruning mechanism validates that behavior remains unchanged with respect to tests and existing contracts before proposing inline replacements or deletions.

Avoid code pruning when behavior validation against tests is incomplete or missing. Since pruning proposes deletions to reduce complexity, lacking test coverage makes it difficult to validate that behavior remains unchanged.