project-graveyardlisted

# Project Graveyard 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. ## When to use - 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. ## When not to use - 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 - Analyzing one specific repo's history in depth — just read the git log ## Run it ```bash python3 scripts/graveyard.py ~/dev ~/projects ``` Point it at wherever projects actually live. If you don't know where that is, ask — one question beats sweeping someone's home directory uninvited. No args scans the usual suspects (~/dev, ~/projects, ~/code, ~/Desktop, ...). Useful flags: - `--days 90` — how long silent before a repo counts as dead (default 45) - `--json report.json` — full machine-readable data - `--me work@email.com` — claim commits made under other emails