warden — Claude Code skill: what it does, how to install
Runs Warden to analyze uncommitted code changes or git revisions before you commit. Catches issues early and can apply suggested fixes automatically.
npx skills add getsentry/warden --skill warden -a claude-codeWhat warden does
Warden evaluates modified files, git ranges like main..HEAD, or specific file paths against triggers defined in warden.toml. Findings are grouped into high, medium, and low severities. The CLI exits with code 1 when findings reach the specified fail threshold, such as --fail-on high.
The tool can automatically patch code with the --fix flag. It also manages project configuration: warden init scaffolds warden.toml along with GitHub workflows, while warden sync refreshes cached remote skills.
You must set WARDEN_MODEL and the matching WARDEN-prefixed provider API key before running any checks. Without these environment variables, analysis cannot execute.
What it helps with
- inspect uncommitted diffs before creating a git commit
- automatically apply suggested code fixes with
--fix - initialize project configuration files and GitHub workflows
- filter analysis to a specific skill or list of files
Example prompts for the agent
- Run warden on my uncommitted changes
- Run warden main..HEAD and automatically apply fixes
- Initialize warden.toml and GitHub workflow for this repository
How to install warden
1Skills CLI (Vercel)
npx skills add getsentry/warden --skill warden -a claude-code2Manually: put the files in place
~/.claude/skills/warden/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/warden/
1Skills CLI (Vercel)
npx skills add getsentry/warden --skill warden -a codex2Manually: put the files in place
.agents/skills/warden/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add getsentry/warden --skill warden -a cursor2Manually: put the files in place
.cursor/skills/warden/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install getsentry/warden warden2Manually: put the files in place
.github/skills/warden/SKILL.md1Skills CLI (Vercel)
npx skills add getsentry/warden --skill warden -a gemini-cli2Platform CLI
gemini skills install https://github.com/getsentry/warden --path skills/wardenManually: put the files in place
.devin/skills/warden/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add getsentry/warden --skill warden -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about warden
How to install warden in Claude Code?
Run npx skills add getsentry/warden --skill warden -a claude-code in your terminal.
What does warden do?
It reviews local code modifications against triggers defined in warden.toml. It flags issues by severity and can apply suggested patches directly using --fix.
What environment variables does warden require?
Set WARDEN_MODEL and the corresponding WARDEN-prefixed provider API key for that model before running the command.
Source text
SKILL.md · Apache-2.0
--- name: warden description: 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. --- Run Warden to analyze code changes before committing. ## References Read the relevant reference when the task requires deeper detail: | Document | Read When | |----------|-----------| | `<skill-root>/references/cli-reference.md` | Full option details, per-command flags, examples | | `<skill-root>/references/configuration.md` | Editing warden.toml, triggers, patterns, troubleshooting | | `<skill-root>/references/config-schema.md` | Exact field names, types, and defaults | | `<skill-root>/references/creating-skills.md` | Writing custom skills, remote skills, skill discovery | ## Running Warden ```bash # Analyze uncommitted changes (uses warden.toml triggers) warden # Run a specific skill warden --skill <skill-name> # Analyze specific files warden src/auth.ts src/database.ts # Analyze changes from a git ref warden main..HEAD warden HEAD~3 # Auto-apply suggested fixes warden --fix # Fail on high-severity findings warden --fail-on high ``` Set `WARDEN_MODEL` and the WARDEN-prefixed provider API key for that model before running. ## Pre-Commit Workflow After making code changes and before committing: 1. Run `warden` to analyze uncommitted changes 2. Review the findings 3. Fix issues Warden reports (or use `warden --fix` to auto-apply) 4. Commit the changes Run Warden once to validate work. Do not loop re-running Warden on the same changes. ## Reading Output **Severity levels:** - `high` - Must fix before merge - `medium` - Worth reviewing - `low` - Minor improvement **Exit codes:** `0` = no findings at or above fail threshold. `1` = findings at or above fail threshold. **Verbosity:** `-v` shows real-time findings. `-vv` shows debug info (tokens, latency). `-q` shows errors and summary only. ## Commands | Command | Description | |---------|-------------| | `warden` | Run analysis (default) | | `warden init` | Initialize warden.toml and GitHub workflow | | `warden add [skill]` | Add skill trigger to warden.toml | | `warden sync [remote]` | Update cached remote skills | | `warden setup-app` | Create GitHub App via manifest flow | For full options and flags, read `<skill-root>/references/cli-reference.md`.
© getsentry · Apache-2.0 · getsentry/warden