Eve Repo Upkeep

Keep an app repo current with Eve conventions. The checks are independent — run them in parallel when multiple areas need attention.

When to Use

• After Eve platform updates or manifest schema changes
• Before a major deploy or release
• When onboarding a new maintainer

Phase 1: Assess

Quickly determine which areas need attention. Check which of these files exist and whether they look stale — don't deep-read every file, just note which areas need work:

• .eve/manifest.yaml — does it exist? Is the schema line eve/compose/v1?
• skills.txt — does it exist? Are there pinned or obsolete entries?
• AGENTS.md / CLAUDE.md — do they reference current skills?
• agents/ directory — do agents.yaml, teams.yaml, chat.yaml exist?
• Codebase — any obvious deprecated CLI patterns or inline secrets?