What problem does it solve? Removing unused code is risky: code that looks dead may be reached through dynamic entry points like routes, events, reflection, or feature flags, and deleting it can silently break the system. This Skill enforces a proof-based dead code removal workflow that only deletes what is verifiably dead and flags everything else as a suspicious orphan. ## 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 any candidate as dead. - Business-rule safeguard: Cross-checks candidates against the project's soul.md and confirmed specs so code implementing a confirmed business rule is never removed, even if it appears unused. - Gated, reversible removal: Generates a self-contained plan.html report, requires explicit approval of the removal diff, and records every change as a revertible CHG-NNN.diff file. - Use Case: During a refactoring cycle, you suspect several functions and modules are unused. Run this Skill to get a per-snippet proof of death, an approval gate showing the exact removal diff, and a report listing suspicious orphans that were deliberately kept. ## Quick Start Ask the agent to run /reversa-prune on a specific opportunity or target, then review the death-proof report and approve the removal diff.
