wa:dev-simplify

To clean up post-development code, scan changed files for duplication, dead code, and poor naming, then apply behavior-preserving refactors. This ensures the codebase stays maintainable without altering observable functionality.

Yes, refactoring can target only the files changed in your current feature branch's git diff. This scopes the simplification process strictly to your latest modifications rather than scanning the entire codebase.

Yes, the code simplification workflow includes stage orchestration that validates applied refactors via test and lint checks. This ensures changes do not break existing behavior or introduce style violations.

The best way to remove dead code safely is using behavior-preserving edits that explicitly avoid refactors altering program logic. This targets redundancy and complexity while maintaining the original observable output.

You should avoid automated code simplification if your branch lacks test coverage or if your changes involve complex logic that cannot be safely refactored without altering observable behavior.