codebase-cleanup

Pre-release codebase cleanup removes dead code paths, stray logs, and temporary files while preserving functional behavior. It flags uncertain deletions for review and requires linting and tests to pass after cleanup, ensuring safe production releases.

Conservative dead code removal deletes code paths with explicit references or no impact while flagging uncertain cases for manual review. It preserves git history readability and enforces linting and basic tests to pass before confirming any deletion.

Codebase cleanup applies across both production- and feature-branch workflows. It handles dead code elimination, debug artifact hygiene, and configuration audits conservatively, making it suitable for pre-release cleanup at any branch stage.

Security and configuration audits identify misconfigurations, secrets left in repo, and risky artifacts during codebase cleanup. They flag or remove these issues with care, reducing the attack surface area for production releases without altering functionality.

Conservative codebase cleanup removes dead code, debug artifacts, and security risks while preserving functional behavior. It enforces conservatism by flagging uncertain deletions, maintaining git history readability, and requiring linting and basic tests to pass.

Avoid automatic dead code deletion when code paths lack explicit references or impact analysis is uncertain. Conservative cleanup flags these uncertain cases for review rather than deleting blindly, preventing accidental removal of functional code.