Weekly codebase inspection on a schedule

Code review sees what changed. It doesn't see the module nobody has touched in a year. This template sweeps one area of the codebase on a schedule and turns the worst problem into a change you can review.

Which agents run

Each slice looks at the module from one angle: correctness, security risk (authorization, injection, data exposure, supply chain) and missing tests. The Architect merges them into one ranked summary, which you read on the session page.

The code pass then acts on the task: here, a fix for the most serious item. Keep the module small enough to inspect in one session; agents read a selected snapshot of the repository, not the whole tree.

Gates that apply

The fix goes through the usual quality gates: your test command runs against it, the findings review reads its diff with the slices as context, open high or critical findings block, and a person approves it. Use Fix on a finding to start a session that fixes it.

The rest of the summary is advice. To act on more items, send a follow-up from the session page, one item at a time.

Schedule it

Open Release → Schedules and choose New schedule:

Choose Preview next 5 to check the times, then Create schedule. Run now on the row starts one immediately, and History lists past runs. Rotate the module in the task every few weeks so the sweep covers the whole codebase.

Every run costs model spend, so a per-workflow cap in cost controls keeps a forgotten schedule in check.