mcpField
W
warden-sweep

warden-sweep

github.com/getsentryTesting & quality418285 installsUpdated today
Repository

About warden-sweep

warden-sweep is a repository-wide workflow skill for running Warden scans, validating findings, tracking them, and preparing draft PRs. It guides developers through a resumable, sequential process and organizes the results into a report.

Key features

  1. 01Scan repository files with Warden
  2. 02Verify findings before patching
  3. 03Create a tracking issue
  4. 04Patch findings and open draft PRs
  5. 05Resume runs and organize reports

Use cases

  1. 01Review a repository for Warden findings
  2. 02Validate findings before creating fixes
  3. 03Track verified work in an issue and draft PRs

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/getsentry/warden --skill warden-sweep

After installing, type/warden-sweepin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

SOURCES.md
SPEC.md
references/
issue-phase.md
organize-phase.md
patch-phase.md
patch-prompt.md
resume-and-artifacts.md
scan-phase.md
script-interfaces.md
verify-phase.md
verify-prompt.md
scripts/
_utils.py
create_issue.py
extract_findings.py
find_reviewers.py
generate_report.py
index_prs.py
organize.py
scan.py

Details

From the project README

Warden Sweep

Run a full-repository Warden sweep: scan files, verify findings, create a tracking issue, open draft PRs for validated issues, and organize the final report.

Requires: warden, gh, git, jq, uv.

Run commands from the repository root. Use the host's skill-root path for bundled scripts and references.

Output goes to .warden/sweeps/<run-id>/.

References

Load only the reference for the current phase:

NeedRead
Script arguments, outputs, and side effectsreferences/script-interfaces.md
Phase 1 scan workflowreferences/scan-phase.md
Phase 2 verification workflowreferences/verify-phase.md
Phase 3 tracking issue workflowreferences/issue-phase.md
Phase 4 patch and draft PR workflowreferences/patch-phase.md
Phase 5 organize and final report workflowreferences/organize-phase.md
Resume behavior and artifact layoutreferences/resume-and-artifacts.md
Verification task prompt templatereferences/verify-prompt.md
Patch task prompt templatereferences/patch-prompt.md

Workflow

Track progress across phases:

  • 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

After organizing, report:

## Sweep Complete

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

Full report: `{summaryPath}`

Comments

Markdown supported