corpse-reviver

Extract dead code fragments from Git history and store them with provenance metadata.

Updated Nov 30, 2025

Search Tags:#provenance #data-transformation #git-history #dead-code #code-archaeology #necromancy

Ready to run

npx skills add https://github.com/poisontr33s/chthonic-archive --skill corpse-reviver

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: corpse-reviver
Source: https://github.com/poisontr33s/chthonic-archive/tree/main/.codex/skills/corpse-reviver
Command: npx skills add https://github.com/poisontr33s/chthonic-archive --skill corpse-reviver

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Prowling the wasteland for dying, unreferenced, or dead code and turning it into provenance-backed fragments that can be reassembled into living composites.

Core Features & Use Cases

Harvest dead code from multiple graveyards (commits, stashes, reflog, comments, and orphaned/untracked files) and classify by language.
Embalm fragments with provenance, store in a vault, and enable reanimation via a search and stitch workflow.
Use cases include code recovery after refactors, archival of historical fragments, and building new composites from existing code.

Quick Start

Snapshot a few files before edits, then run harvest to populate the vault and reanimate fragments as needed.

Frequently Asked Questions about corpse-reviver

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I recover dead code from Git history and stashes?▼

Dead code fragments are harvested from Git history, stashes, reflogs, dead branches, commented blocks, and untracked files, then classified by language and stored in a vault with provenance metadata for later recovery.

What is code archaeology for extracting dormant fragments from reflogs?▼

Code archaeology is the deterministic harvesting of dormant or dead code fragments from reflogs, dead branches, and commented blocks, embalming each fragment with provenance and storing them in a language-classified vault for reassembly.

Can I reassemble historical code fragments into new composites?▼

Historical code fragments are reassembled through a delta-based stitching workflow that searches the vault and sutures provenance-backed fragments into living composites for reproducible code reassembly.

How do I archive commented blocks and untracked files with provenance metadata?▼

Commented blocks and untracked files are archived by harvesting them into a language-classified vault, embalming each fragment with provenance metadata that tracks its origin for later search and reanimation.

Does this code recovery workflow work without external dependencies?▼

The code recovery workflow operates with no external dependencies, relying solely on internal scripts to harvest, classify, vault, and stitch fragments from Git reflogs, stashes, and orphaned files.

What's the best way to extract dead code after a major refactor?▼

Extracting dead code after a refactor involves harvesting unreferenced fragments from Git history and stashes, classifying them by language, and vaulting them with provenance for later reanimation into new composites.