Graveyard: a funeral for dead code, with a checker that keeps the AI honest

Description and use

Graveyard turns deleted git files into a client‑side cemetery, using a local Gemma 3 4B model to generate verified epitaphs while preventing hallucinations.

Problem

Repositories accumulate deleted files that are never revisited, creating a hidden legacy of dead code.

Outcome

Graveyard provides a visual, client‑side cemetery for deleted code, using a local open‑weight model to generate verified epitaphs while preventing hallucinations.

Workflow

• Run a Node script that reads the git history and outputs a JSON file of deleted files.
• Load the JSON into a client‑side web page that renders a cemetery of tombstones.
• For each tombstone, call a local Gemma 3 4B model via Ollama to generate an epitaph and cause of death.
• Apply a checker that ensures dates, file names and commit hashes come from the repo, and that the cause of death shares most keywords with the real commit message; otherwise replace with "Cause of death unknown".
• Display the verified tombstone data to the user.

Evidence

A small Node script reads a git repo's history (read-only) and exports every deleted file as JSON.

Source

The app calls only http://localhost:11434. A guard in the code throws if the model name doesn't start with "gemma", and there are no API keys anywhere in the app.

Source

Tests: 15 unit tests for the checker, all passing.

Source