Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
getsentry avatar

Warden Sweep

  • 114 installs
  • 358 repo stars
  • Updated August 4, 2026
  • getsentry/warden

Warden full-repo sweep scanning all files, verifying findings, and opening draft PRs.

About

Warden full-repository sweep skill. Scans every file with Warden analysis, verifies findings through deep tracing to reduce false positives, and creates draft PRs for validated issues. Triggered when asked to sweep the repo, scan all files, or run comprehensive code review. Combines automated detection with verification before opening PRs, ensuring only substantiated findings reach reviewers. Part of the Warden agent family for Sentry codebase quality at scale.

  • Full-repository scan of every file with Warden analysis
  • Deep tracing verification before reporting findings
  • Draft PR creation for validated issues only
  • Triggers on sweep the repo or scan all files requests
  • False positive reduction through verification pass

Warden Sweep by the numbers

  • 114 all-time installs (skills.sh)
  • Ranked #432 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

warden-sweep capabilities & compatibility

Capabilities
scan all files · verify findings · create draft prs
Works with
github · sentry
Use cases
code review · security audit
From the docs

What warden-sweep says it does

Scans every file with Warden, verifies findings through deep tracing, creates draft PRs for validated issues.
SKILL.md
npx skills add https://github.com/getsentry/warden --skill warden-sweep

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs114
repo stars358
Last updatedAugust 4, 2026
Repositorygetsentry/warden

How do I run a comprehensive code quality sweep across the entire repository?

Run a full-repository Warden code sweep scanning every file, verifying findings via deep tracing, and creating draft PRs for validated issues.

Who is it for?

Teams requesting full-repository Warden scans with PR-ready fixes.

Skip if: Single-file reviews or manual code review without Warden automation.

When should I use this skill?

User asks to sweep the repo, scan all files, or run comprehensive Warden review.

What you get

All files scanned, findings verified, and draft PRs opened for validated issues.

Files

SKILL.mdMarkdownGitHub ↗

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}`

Related skills

FAQ

Does every finding become a PR?

Only validated findings after deep tracing verification get draft PRs.

What does deep tracing do?

Verifies findings through code path analysis to reduce false positives.

How much of the repo is scanned?

Every file in the repository is included in the sweep.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.