Gravekeeper: a Día de los Muertos cemetery for dead code

Description and use

Gravekeeper builds an offline cemetery for dead code, mining its Git history and generating memorial cards via Gemini.

Problem

Repositories accumulate dead code—files, exports, and dependencies that are never used—yet developers lack a systematic way to document and honor the removal of such code.

Outcome

Gravekeeper produces a visual, offline cemetery of dead code and a markdown memorial that records the lifecycle and removal rationale of each dead file, enabling transparent maintenance and historical insight.

Workflow

• Run node src/index.ts scan <repo> to collect dead files using knip and git forensics.
• Run node src/index.ts write <repo> to send batches of dead-file records to Gemini and receive strict JSON epitaphs.
• Run node src/index.ts render <repo> to combine census and epitaphs into a self‑contained HTML cemetery and a graveyard.md file.
• Open the generated graveyard.html locally to view the cemetery.
• Commit graveyard.md alongside a removal PR to preserve the removal rationale.

Evidence

Gravekeeper calls them what they are — the dead — and gives them the send‑off the calendar demands.

Source

Three rites, three commands, against any JS/TS repo: ...

Source

The result is a candlelit cemetery you can walk through in the browser — tombstone cards, candle glow, marigold palette — plus a graveyard.md you can commit next to the removal PR, so the reason those lines are gone never evaporates with the conversation that decided it.

Source