project-graveyard

A skill in Shubhamsaboo/awesome-llm-apps · 145,077 stars on GitHub

Scans the developer's machine for dead side projects, autopsies each one from its git history (died at the payments wall, killed by a newer project, finished but never shipped), surfaces their personal death patterns, and picks the corpse most worth resurrecting — then helps ship it. Use when the user mentions abandoned, unfinished, or old side projects, asks "what should I finish", wants to revive or resurrect a project, says "run the graveyard", wonders why they never finish anything, or is about to start a new project that sounds like one they already built. Runs entirely locally.

Security grade of this SKILL.md: SAFE · how we grade

How to install project-graveyard

npx skills add Shubhamsaboo/awesome-llm-apps --skill project-graveyard -a claude-code

The skills CLI copies this one skill into Claude Code (use -a for another agent). Or read its SKILL.md on GitHub.

What the SKILL.md says

Every developer has a folder full of dead projects. Nobody has ever gotten an autopsy report. This skill scans the machine for abandoned repos, works out why each one died from its git history, finds the user's personal death patterns, and picks the one corpse worth digging up — then helps ship it. Everything runs locally. No API, no network, nothing leaves the machine. The user asks about abandoned/unfinished/old side projects, or what to finish. The user wants to revive, resurrect, or "finally ship" something. The user asks why they never finish projects. The user proposes a new project — check the graveyard first (see Necromancer mode). There's a decent chance they already built half of it. Cleaning up disk space or node_modules — that's kondo/npkill, not this. Archiving repos on GitHub — this works on local clones and never-pushed work.

Other skills in Shubhamsaboo/awesome-llm-apps

  • advisor-orchestrator-worker Use when a task is too large for one model pass, needs parallel research or generation across many subtasks (like researching a dozen compe…
  • commit-archaeologist Reconstructs why code exists from local git history, including the introducing commit, later changes, current authors, repeated companion f…
  • dependency-doctor Checks requirements.txt, pyproject.toml, and package.json dependency manifests for surface-level direct-dependency footguns: standard-libra…
  • first-reader Beta readers for any draft, run by simulating how a real reader experiences it, moment by moment. A skim gate, a no-lookahead timed read pr…
  • scope-creep-detector Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad pull requests, changes that grew beyond a fix, dep…
  • thinking-out-loud A contract for what the agent does when a long, messy, stream-of-consciousness ramble arrives (usually voice dictation): act on nothing unt…