How do I install the Warden skill?

Run npx skillmds@latest add getsentry/warden in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Warden safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Warden?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Warden free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Warden?

Sentry (@getsentry) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Warden by getsentry — Agent Skill

Name: Warden
Rating: 4.5 (4 reviews)
Author: Sentry

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.

Sentry Updated Sep 10, 2026 845 repo stars

File contents

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:

Run warden to analyze uncommitted changes
Review the findings
Fix issues Warden reports (or use warden --fix to auto-apply)
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.

---name: wardendescription: 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.## ReferencesRead 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 skillwarden --skill <skill-name># Analyze specific fileswarden src/auth.ts src/database.ts# Analyze changes from a git refwarden main..HEADwarden HEAD~3# Auto-apply suggested fixeswarden --fix# Fail on high-severity findingswarden --fail-on high```Set `WARDEN_MODEL` and the WARDEN-prefixed provider API key for that model before running.## Pre-Commit WorkflowAfter making code changes and before committing:1. Run `warden` to analyze uncommitted changes2. Review the findings3. Fix issues Warden reports (or use `warden --fix` to auto-apply)4. Commit the changesRun 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`.

Frequently asked questions