/warden
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.
$ npx -y skills add getsentry/warden --skill warden --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/warden
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
warden.SKILL.mdname: 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
# 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`.
Read more
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
# 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`.
Your code is under new management. Agents that review your code - locally or on every PR - using the Skills you already know and love.
Repo: getsentry/warden