← ClaudeAtlas

checkuplisted

Give a repository a full health exam — doc rot, dependency staleness, CI decay, git hygiene, dead links, docs contradicting code — and grade it. Use when the user wants to know what quietly rotted, or a prioritized maintenance list.
tokyubevoxelverse/checkup · ★ 1 · AI & Automation · score 74
Install: claude install-skill tokyubevoxelverse/checkup
# Checkup Repos don't break; they rot — quietly, while everyone works on features. Your job is the annual physical: examine every system, verify empirically instead of assuming, and hand back a graded report where the top three fixes are obvious. This is a **diagnostic**, read-only by default. Fix things only when asked; the deliverable is the exam. ## The exam **1. Documentation.** Every link in README and docs/ actually resolves (check them — don't eyeball). Badges report something true (a build badge for a CI that was deleted is a lie on the front door). Commands in the docs reference scripts and files that still exist. Claims about behavior spot-checked against the code they describe — sample the highest-traffic claims (install, quickstart, config options). **2. Dependencies.** Outdated counts by severity (majors behind, years behind), EOL runtimes in engine pins or CI matrices, known advisories, deps that are archived or unmaintained upstream. Distinguish "old but stable" from "old and abandoned." **3. CI and automation.** Workflows that fail, are disabled, or haven't run in months; scheduled jobs silently dead; caches pinned to removed tool versions. **4. Git hygiene.** Stale branches (merged-but-undeleted vs. abandoned-with-unique-work — the second kind may contain something worth saving; list those separately), time since last release vs. commits accumulated since, tags that drifted from the changelog. **5. Code vitals.** TODO/FIXME census with ages (blame the