code-cleanup

To safely remove dead code, this Skill audits repositories across multiple maintenance dimensions in parallel, applying only high-confidence hygiene fixes while surfacing ambiguous findings for human review.

Resolving circular dependencies and consolidating weak types is handled by running parallel static analysis audits across the codebase, applying safe edits to tighten types and prune legacy fallbacks without rewriting the architecture.

To verify code cleanup changes, this Skill uses a verify-and-repair pass that re-runs the target's checks after editing and compares post-change results against a pre-cleanup baseline to automatically catch regressions.

Yes, this code refactoring tool specifically targets defensive try/catch removal and legacy fallback pruning alongside dead-code removal, applying safe high-confidence edits to reduce implementation clutter.

No specific dependencies are required to run this static analysis cleanup tool, but you must provide a valid target repository path for the parallel audits and subsequent verify-and-repair loop to function.

The limitation of this automated code hygiene approach is that it only applies clearly justified changes to reduce complexity, meaning ambiguous findings are left untouched and surfaced for manual human review rather than auto-fixed.