What problem does it solve?
Developers accumulate folders of unfinished side projects without understanding why each one stopped. This Skill reads local git history to diagnose the cause of death for every abandoned repo, surface personal abandonment patterns, and identify which corpse is closest to shipping.
Core Features & Use Cases
- Cause-of-Death Autopsy: Classifies each dead repo into categories like shiny_object, deploy_fear, payments_wall, auth_wall, boilerplate_wall, rewrite_spiral, scope_explosion, or slow_fade based on forensic git evidence.
- Pattern Detection: Identifies recurring developer habits such as projects dying at a specific day count or being killed by newer side projects.
- Pulse Ranking: Scores each corpse 0-100 on resurrectability based on README presence, tests, commit momentum, and deploy readiness.
- Resurrection Planning: Generates a 7-step plan ending at shipped, with a world-check for APIs or tools that may have made the original blockers easier.
- Relapse Watch: Tracks previously resurrected projects across scans and reports whether they are holding or going silent again.
- Use Case: A developer asks "why do I never finish my side projects?" The agent scans ~/dev and ~/projects, produces a tombstone report naming each corpse with its cause, surfaces the pattern that four of six projects died at day 19, and offers to resurrect the strongest pulse candidate.
Quick Start
Run the graveyard on my ~/dev and ~/projects folders and tell me which project is closest to shipping.