// 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.
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.
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.
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.
| name | scan-codebase |
| description | 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. |
Read these shared references when needed:
../shared/references/findings.schema.md../shared/references/findings.lifecycle.mdRun a fresh review pass from code and docs into findings.
test-codebase; if runtime validation is needed, hand off there.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 scan scope. Confirm the effective variables first:
pathdepthStart from fresh context. Read current code, docs, tests-as-code, routes, schemas, migrations, and adjacent design material before looking at existing findings.
Produce findings from review. Surface correctness, consistency, completeness, soundness, functionality, security, performance, compatibility, migration, and missing-test findings when supported by evidence.
Update the active findings record.
Use path/findings.md.
Hand off when execution is needed.
Use triage-findings for discussion and planning, test-codebase for validation, and resolve-findings for implementation.