warden-sweep

Point it at a whole codebase and walk away: it works through every file, throws out the findings it cannot stand behind, and comes back with a counted report and a pile of proposed fixes waiting for someone to approve.

When to use

SCOPE

USE FOR

Scan an entire repository with Warden instead of just a diff.
Verify every automated finding before it becomes a code change.
Open a draft PR per validated finding, branched from the default branch.
Track a repo-wide sweep's progress under a single tracking issue.
Resume an interrupted sweep from its first incomplete phase.

This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.

In this document (6)

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:

Need	Read
Script arguments, outputs, and side effects	`references/script-interfaces.md`
Phase 1 scan workflow	`references/scan-phase.md`
Phase 2 verification workflow	`references/verify-phase.md`
Phase 3 tracking issue workflow	`references/issue-phase.md`
Phase 4 patch and draft PR workflow	`references/patch-phase.md`
Phase 5 organize and final report workflow	`references/organize-phase.md`
Resume behavior and artifact layout	`references/resume-and-artifacts.md`
Verification task prompt template	`references/verify-prompt.md`
Patch task prompt template	`references/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

Read references/script-interfaces.md once before running scripts.
Run Phase 1 from references/scan-phase.md. Save runId and sweepDir.
Run Phase 2 from references/verify-phase.md. Verify every finding before patching.
Run Phase 3 from references/issue-phase.md. Continue if issue creation fails.
Run Phase 4 from references/patch-phase.md. Patch sequentially, one finding at a time.
Run Phase 5 from references/organize-phase.md.
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}`

Not standalone. This skill ships with getsentry/warden and only works together with that tool — install the tool first, then add this skill.

Run this outside your AI tool, using Node.js 22.20.0 or newer. Skills CLI 1.7.2 skips skill selection; prompts cancel installation without an interactive terminal. If choosing Project when asked about installation scope, open your project's folder before running this.

Install checklist

Check selected tools if a picker appears; Claude Code may be unchecked under Additional agents. ↑/↓ moves, Space toggles selections, Enter confirms.
Without a tool picker, check Installing to: for your intended tool. Stop if it names a different tool.
If asked, choose Symlink (Recommended) for shared files or Copy to all agents for separate copies; review the summary before confirming installation.
Install the find-skills skill? defaults to Yes, adding another skill for all projects. Choose No if you don't want that extra installation.

Skills CLI 1.7.2 sends install data to skills.sh by default, including the source, skill names, target tools and file details; GitHub sources are reported only when GitHub confirms the repository is public, while other remote sources can also be reported. Confirmed-public GitHub sources also trigger a security-audit request. Before installing, set the environment variable DO_NOT_TRACK=1 or DISABLE_TELEMETRY=1 to disable both.

npx skills add getsentry/warden --skill "warden-sweep" --full-depth

Once this skill is installed where Claude Code loads it, type /warden-sweep in Claude Code when you want to start it. Claude Code won't start this skill on its own.

What's inside

Files included with this skill.

View on GitHub

Warden Sweep

References

Workflow

Phase Order

Non-Negotiable Rules

Final Response

Account or credentials required

What's inside

More skills

agent-prompt

architecture-review

code-review

security-review

skill-writer

warden