Skip to main content

Upkeep

In brief: Upkeep maintains the suite over time—TrueCoverage and requirements gaps, optional ExploreChimp, cleanup; synonym of /testchimp evolve.

When to use​

Use Upkeep on a cadence (for example weekly) or after deploys 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.

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 upkeep run, 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:

  1. author-plans
  2. connect-to-test-env
  3. fix-coverage-gaps
  4. run-explorechimp
  5. cleanup
  6. instrument-truecoverage

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, 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​

FAQ

Who should run /testchimp audit?

Tech leads, QA champions, or agents before sprint planning—to prioritize infra, plans, and SmartTests with the highest product risk.

What does audit check?

Unlinked scenarios, failing CI trends, TrueCoverage holes on frequent events, stale plans, and unresolved exploration bugs.

How is audit different from evolve?

Audit diagnoses and reports; evolve actively expands coverage, updates fixtures, and runs explorations based on similar intelligence.

Related documentation