What problem does it solve? Decommissioning code is risky: deleting a subsystem without a verified footprint breaks living code, and losing the deleted implementation makes future recovery impossible. This Skill runs a structured burial ritual that archives code into a graveyard repository before anything is deleted, keeping the living repo green throughout. ## Core Features & Use Cases - Footprint Verification: Classifies candidate files by imports and symbols rather than filenames, sweeping shared files for hidden wiring like metrics registrations, alert rules, config structs, and registry entries. - Two-PR Burial Ritual: Merges an interment PR into the graveyard repo (verbatim code copy, tombstone, index entry) before any deletion PR touches the living repo, which must pass build, vet, lint, and tests. - Gated Data Handling: Optionally seals database dumps with age encryption before any table drop, and supports full-repo retirement via encrypted git bundles plus deliberate exhumation procedures. - Use Case: When retiring a deprecated microservice, use this Skill to verify nothing living imports it, archive its code and schema into the graveyard with a tombstone, then delete it from the monorepo with a green CI gate. ## Quick Start Ask the assistant to bury the named subsystem or repository, for example by saying "bury the legacy notifications service and keep its memory in the graveyard".
