Warden Sweep

warden

gh

git

jq

uv

.warden/sweeps/<run-id>/

References

references/script-interfaces.md

references/scan-phase.md

references/verify-phase.md

references/issue-phase.md

references/patch-phase.md

references/organize-phase.md

references/resume-and-artifacts.md

references/verify-prompt.md

references/patch-prompt.md

Workflow

• Phase 1: Scan repository files with Warden.
• Phase 2: Verify findings before patching.
• Phase 3: Create a tracking issue.
• Phase 4: Patch verified findings and open draft PRs.
• Phase 5: Organize results and produce the final report.

Phase Order

1. Read

   references/script-interfaces.md

   once before running scripts.
2. Run Phase 1 from

   references/scan-phase.md

   . Save

   runId

   and

   sweepDir

   .
3. Run Phase 2 from

   references/verify-phase.md

   . Verify every finding before patching.
4. Run Phase 3 from

   references/issue-phase.md

   . Continue if issue creation fails.
5. Run Phase 4 from

   references/patch-phase.md

   . Patch sequentially, one finding at a time.
6. Run Phase 5 from

   references/organize-phase.md

   .
7. For interrupted or partial runs, read

   references/resume-and-artifacts.md

   and continue from the first incomplete phase.

Non-Negotiable Rules

• Verify findings before creating fixes.
• Use draft PRs for generated patches.
• Branch every patch from the repository default branch.
• Patch findings sequentially; do not run patch workers in parallel.
• Skip existing entries in sweep artifacts instead of duplicating work.
• Record failures in sweep data and continue to the next finding when possible.
• Clean up each worktree after patch success or failure.

Final Response

## Sweep Complete

| Metric | Count |
|--------|-------|
| Files scanned | {filesScanned} |
| Findings verified | {verified} |
| PRs created | {prsCreated} |
| Security findings | {securityFindings} |

Full report: `{summaryPath}`