Nightly Fix Sweep
Turn a night's open code findings into reviewable change proposals: triage the leads, cluster what belongs together, and draft one focused proposal per cluster for the user to read and apply in the morning. The project's files are never touched.
Steps
Entry step: triage. Each step names the specialist role it wants; the full working prompt is expandable.
- Triage the leads into clustersdeveloperentry
Show working prompt
You have been handed open findings to sweep: {{leads}}. The task description may carry more detail per lead. Read the affected files and judge each lead against the CURRENT code: real, already fixed, stale, or a judgement only the owner can make. Leaving a lead out is legitimate — say why rather than forcing a change to satisfy a stale review. Cluster what belongs together as ONE change: a fix that spans a file and its caller is one cluster, not two — splitting it would hand the user two half-changes neither of which stands alone. At most 8 clusters; prefer fewer, focused ones. Write ONE `write_task_note` starting with the line `## Triage`: per lead, whether you will fix it and which cluster it belongs to, with reasons for anything left out. Then write the cluster list to the artifact `{{workPath}}/clusters.json` with ONE `write_artifact` call: a JSON array where each entry is an object with exactly these string fields — `slug` (short kebab-case name for the cluster, e.g. "auth-null-guard"), `issueRefs` (the refs in that cluster, comma-separated), and `focus` (one sentence on what that cluster should change). If nothing is worth fixing, write an empty array `[]` and say why in your note. - Draft the proposals
Show working prompt
Your clusters are being drafted, one proposal per cluster. Wait for the shards to finish, then call `advance_task_step`.
- Hand over
Show working prompt
The sweep is done. Write one short `write_task_note` naming the proposals your crew drafted (by cluster) and any leads deliberately left alone with their reasons, then call `advance_task_step`. Never claim anything was fixed or applied — these are proposals for the user to review.
Triggers
Phrases that suggest this craftbook to a crew.
- sweep the open findings
- nightly fixes
- draft fixes for the open issues
- fix the boekwachter findings
Source
View this craftbook on GitHub · MIT license