// Run or inspect the relevant validation paths and turn failures, regressions, or missing coverage into findings. Accept optional `path` and `depth` parameters and default to `path=infer`, `depth=deep`. Confirm effective variables before starting.
| name | test-codebase |
| description | Run or inspect the relevant validation paths and turn failures, regressions, or missing coverage into findings. Accept optional `path` and `depth` parameters and default to `path=infer`, `depth=deep`. Confirm effective variables before starting. |
Read these shared references when needed:
../shared/references/findings.schema.md../shared/references/findings.lifecycle.mdRun validation-oriented testing work and convert the result into findings.
Accept a depth parameter from the prompt:
shallowdeepDefault:
depth=deepAccept an optional path from the prompt.
path is provided, use it as the local design or findings folder.path is omitted, infer it from the branch, subsystem, or matching docs and state the inferred value before starting.Default:
path=inferEstablish validation scope. Confirm the effective variables first:
pathdepthChoose the validation surface. Use existing tests first when they are relevant. Add targeted repro or smoke execution when that is the shortest way to validate behavior.
Run or inspect. Execute the chosen tests or repro steps when possible. If execution is blocked, record the blocker and its impact explicitly.
Turn outcomes into findings. Capture broken behavior, flaky behavior, missing coverage, missing assertions, environment gaps, and rollout risks in the active findings record.
Update the active findings record.
Use path/findings.md.
Hand off when review or implementation is needed.
Use triage-findings for follow-up questions and planning.
Use resolve-findings when the intended fix path is clear.
Audit and update the supported LLM model list in assets.py against litellm's registry (models.litellm.ai). Use when adding new models, pruning outdated ones, or verifying the list is correct.
Sync the findings record against local review artifacts and optionally a GitHub PR. Accept optional `path` and GitHub PR `url`; when `url` is provided, sync against both remote PR state and local state, otherwise default to local-only sync. Default to `path=infer`. Confirm effective variables before starting.
Update the API reference documentation by downloading the latest OpenAPI spec from production and regenerating the Docusaurus API docs
Resolve findings by implementing the chosen fix path in code, tests, or docs. Accept optional `path` and a `priority` selector; by default resolve only the next highest remaining priority bucket, in order `P0`, `P1`, `P2`, `P3`. Also accept explicit levels or `all`. Default to `path=infer`. Confirm effective variables before starting.
Perform a fresh-context scan of code and docs that turns verification observations and missing-test gaps into findings. Accept optional `path` and `depth` parameters and default to `path=infer`, `depth=deep`. Confirm effective variables before starting.
Coordinate findings work with the user, decide whether scan, test, or sync should run, and turn the current findings set into a ready plan. Accept optional `path` and GitHub PR `url`; default to `path=infer`. Confirm effective variables before starting.