Published Updated
Upkeep
In brief: Upkeep is functional-suite maintenance—TrueCoverage and requirements gaps, optional ExploreChimp, cleanup; synonym of
/testchimp evolve.
When to use
Use Upkeep when you want portfolio maintenance: close coverage gaps, explore hot UX paths, prune redundancy, and keep TrueCoverage instrumentation current. Prefer Run QA for per-PR authoring and regression. Prefer Create Release when cutting a release (Create Release may nest upkeep for MAJOR when policy says so).
Prompt
/testchimp upkeep
/testchimp evolve
/testchimp upkeep for authentication
/testchimp evolve --policy upkeep-weekly.policy.md
Synonyms: /testchimp upkeep, /testchimp evolve, legacy /testchimp audit → catalog id upkeep.
Scope
Scope is optional. When omitted:
- Feature / PR branch — maintain coverage and hygiene around the branch diff.
- Default branch — TrueCoverage / requirements signals and changes since the last
upkeeprun, or a history range you choose.
Optionally limit to a plans folder, product area, or named objective.
Policy
Default file: plans/knowledge/policies/upkeep.policy.md (seeded by init).
Default Subflows:
Tune subflows in policy (for example broader cleanup on monthly runs, skip ExploreChimp when cost-sensitive). Requires connect-to-test-env for executable steps.
What it does
Plan → approve → Execute: update requirements where needed, connect env, bump @testchimp/playwright to latest when behind, close testing gaps from requirements and TrueCoverage, run targeted ExploreChimp, dedupe/prune with cleanup (approval-gated), and extend instrumentation—with full policy-linked traceability.
Orthogonal to cleanup alone: Upkeep includes cleanup as a subflow by default; you can also run Cleanup standalone.
See also
- Run QA — PR / change composite
- Create Release — Ship / release QA posture
- Fix coverage gaps
- Cleanup
- TrueCoverage
FAQ
When should teams run upkeep vs create release?
Use upkeep for portfolio suite maintenance (gaps, cleanup, instrumentation). When shipping, run /testchimp create release—Create Release may nest upkeep for MAJOR when policy says so.
What inputs does upkeep use?
TrueCoverage signals, requirement traceability gaps, CI execution trends, exploration bugs, and markdown plan status.
Can upkeep retire obsolete tests?
Yes—cleanup is a default subflow (approval-gated). Agents can flag or remove tests for removed features when plans and usage signals show they no longer protect product risk.