What problem does it solve? Developers accumulate folders of abandoned side projects with no record of why each one died or which ones are worth finishing. This Skill scans local git repositories, reconstructs the cause of death for each abandoned project from commit history, surfaces personal abandonment patterns, and identifies the project closest to being shippable. ## Core Features & Use Cases - Forensic autopsy from git history: Classifies each dead project by cause (shiny object, deploy fear, payments/auth wall, boilerplate wall, rewrite spiral, scope explosion, slow fade) with evidence lines drawn from commit dates, messages, and touched files. - Pattern detection and pulse ranking: Aggregates statistics like median project lifespan and repeated death causes, then scores each corpse 0-100 on resurrectability based on README, tests, commit count, and deploy config. - Resurrection planning and relapse watch: Produces a step-by-step shipping plan for the top candidate, records resurrections in a state file, and flags projects that go silent again on later scans. - Use Case: Point it at ~/dev and ~/projects to get a tombstone report of 12 dead projects, learn that four were killed by newer projects within days, and receive a 7-step plan to finally ship the one that was 90% done. ## Quick Start Ask your agent to run the graveyard scan on your dev and projects folders and report which abandoned project is most worth resurrecting.
