What problem does it solve? Removing dead 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 logic by requiring a formal proof of death before any removal. ## Core Features & Use Cases - Proof of death: Classifies each candidate as truly dead (no static references and no dynamic entry) or as a suspicious orphan that is never auto-removed. - Soul check: Cross-references candidates against the project's confirmed business rules (soul.md) so confirmed business logic is never treated as dead. - Gated, reversible removal: Generates a self-contained plan.html report, requires explicit approval of the removal diff, and records every change as a reversible CHG-NNN.diff. - Use Case: During a refactoring cycle, run it on a module to get a report of provably dead functions removed with evidence attached, while dynamically-dispatched handlers are flagged as suspicious orphans instead of deleted. ## Quick Start Ask the agent to run reversa-prune on a target module and review the generated removal plan with its death proofs before approving the diff.
