What problem does it solve? Removing unused code is risky: code that looks unused may be reached through dynamic entry points like routes, events, reflection, or feature flags, or may implement a confirmed business rule that is temporarily disconnected. This Skill prevents accidental deletion of live code by requiring formal proof of death before any removal. ## Core Features & Use Cases - Death-proof classification: Scans the full codebase for static references and checks dynamic entry points (routes, events, reflection, string loading, cron, feature flags) before classifying a candidate as dead or as a suspicious orphan. - Soul check: Cross-references candidates against the project's confirmed business rules so that code implementing a confirmed rule is never removed, only flagged. - Gated, reversible removal: Presents a self-contained HTML plan and a removal diff for approval, applies only approved deletions, runs the test suite, and records a reversible CHG-NNN.diff. - Use Case: During a refactoring pass on a legacy service, run this Skill to identify unused functions, get proof that three are truly dead, and keep two others flagged as suspicious orphans because they are reachable via event handlers. ## Quick Start Ask the agent to run /reversa-prune on a target module and approve the removal diff it presents.
