maintenance

name	maintenance
description	Goal-oriented repository maintenance and release-readiness work. Use when the user asks for maintenance, release prep, repo health review, dependency refreshes, spec/docs alignment, test gap review, technical debt analysis, or general cleanup without prescribing an exact sequence.
metadata	{"internal":true}
user-invocable	true

Maintenance

Leave the repo materially healthier and closer to release-ready, with evidence.

Read knowledge/project/maintenance.md first — it owns the success bar, the constraints, and the release-readiness standard. This skill owns execution only. Choose the smallest set of actions that closes the real maintenance risk in front of you; a longer checklist is not a better one.

Sequence

1. Fix the scope. Use the user's scope if given. Otherwise infer one from recent diffs, release posture, and obviously stale areas — and state the assumption.
2. Pick the highest-signal surface first. Recent diffs, failing or flaky checks, stale specs, outdated dependencies, known security or performance hotspots. Skip untouched areas deliberately and say why. Surface-by-surface goals and evidence live in references/surfaces.md.
3. Prefer fixing over reporting. Fix what is small and local. For anything larger, produce a crisp finding with evidence and the next action, and file it in Linear (OSS project, EVE team). Bugs found here prefer a failing test before the fix.