Repo healthcheck — git hygiene, test status, and deep freshness verification of status/directive docs. Gracefully degrades when project-specific conventions (git-erg tickets, STATE.md, etc.) are absent.
Run a healthcheck on the current repository. Report results concisely — one line per check, flag anything abnormal.
This skill is user-level and must gracefully degrade: each check runs only if its prerequisites are present. Missing prerequisites yield a skip status with a one-line reason, never a fail.
gh unavailable.scripts/docs_freshness.shSTATE.mdREADME.md.erg tickets.gh unavailable.## Healthcheck — {date}
| Check | Status | Detail |
|------------------|--------|------------------------------|
| Recent activity | ... | N commits (last 12h) |
| Open PRs | ... | N open |
| Origin sync | ... | synced / ahead N / ... |
| Branch hygiene | ... | N local, N remote |
| Worktrees | ... | N active |
| Orphan commits | ... | none / N found |
| Working tree | ... | clean / N changes |
| Tests green | ... | N passed / K failed |
| Docs freshness | ... | N docs scanned, K stale refs |
Use ok for normal status, warn for attention-needed, fail for problems, skip for gracefully-degraded checks (detail column explains why).
If docs freshness is warn/fail, list each stale finding under the table as one bullet per finding, with the doc, line reference, and the fix (e.g., STATE.md:39 — ticket 0095 listed as TODO but Status: closed (PR #259)). This detail is the point of the deep check — do not compress it into a single line.
After the table (and any stale-findings list), add a one-line summary verdict.