cruft-code-sweep

Dead code removal is performed by coordinating a scanner, historian, and verifier agent to audit your repository, surface risky leftovers, and validate deletions using historical context. This generates a structured safety report with remediation guidance.

Cruft refers to dead code, deprecated patterns, and compatibility hacks lingering in a repository. A code audit identifies cruft using pattern-based detection and history-informed analysis, then verifies safe deletion by checking dependencies, tests, and potential side effects.

Checking deletion safety involves verifying proposed removals against historical context and dependency graphs. The audit process generates a risk assessment that considers dependencies, tests, and potential side effects before recommending any code elimination.

Yes, you can apply the static analysis code audit to any repository to detect cruft. It explores the codebase to surface dead code and risky leftovers, then delivers remediation guidance tailored to the specific dependencies and tests found.

Eliminating compatibility hacks safely requires a coordinated workflow where a scanner finds the hacks, a historian adds time-context, and a verifier validates safe deletion. This approach ensures removals are checked against dependencies and tests to prevent regressions.

Historical context matters because it explains why deprecated code patterns were introduced, helping the verifier validate safe deletion. Without this time-context, removing leftover compatibility hacks risks breaking hidden dependencies or bypassing necessary tests.