warden-sweep
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 |
More from getsentry/warden
architecture-review
Staff-level codebase health review. Finds monolithic modules, silent failures, type safety gaps, test coverage holes, and LLM-friendliness issues.
138warden
Run Warden to analyze code changes before committing. Use when asked to "run warden", "check my changes", "review before commit", "warden config", "warden.toml", "create a warden skill", "add trigger", or any Warden-related local development task.
113agent-prompt
Reference guide for writing effective agent prompts and skills. Use when creating new skills, reviewing prompt quality, or understanding Warden's prompt architecture.
96testing-guidelines
Guide for writing tests. Use when adding new functionality, fixing bugs, or when tests are needed. Emphasizes integration tests, real-world fixtures, and regression coverage.
93find-warden-bugs
Warden-specific bug detection from historical patterns. Targets the architectural seams where bugs have repeatedly occurred: SDK IPC, dual report paths, config threading, concurrent execution, and output rendering.
68notseer
High-precision bug detection. Every report is a proof, not a suspicion. Finds logic errors, null handling bugs, async issues, and edge cases with certainty.
16