// 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.
Finds real correctness bugs in code changes. Use for adversarial code review, bug hunts, regression review, PR correctness review, logic errors, data loss, race conditions, state bugs, interface contract breaks, error handling bugs, edge cases, broken builds, or broken workflows. Excludes style, readability, architecture, AppSec, and best-practice-only feedback unless the issue causes a demonstrable bug.
Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.
Create, synthesize, and iteratively improve agent skills following the Agent Skills specification. Use when asked to "create a skill", "write a skill", "synthesize sources into a skill", "improve a skill from positive/negative examples", "update a skill", or "maintain skill docs and registration". Handles source capture, depth gates, authoring, registration, and validation.
Full-repository code sweep. Scans every file with Warden, verifies findings through deep tracing, creates draft PRs for validated issues. Use when asked to "sweep the repo", "scan everything", "find all bugs", "full codebase review", "batch code analysis", or run Warden across the entire repository.
Reference guide for writing effective agent prompts and skills. Use when creating new skills, reviewing prompt quality, or understanding Warden's prompt architecture.
Staff-level codebase health review. Finds monolithic modules, silent failures, type safety gaps, test coverage holes, and LLM-friendliness issues.
| 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.
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 |
# 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.
After making code changes and before committing:
warden to analyze uncommitted changeswarden --fix to auto-apply)Run Warden once to validate work. Do not loop re-running Warden on the same changes.
Severity levels:
high - Must fix before mergemedium - Worth reviewinglow - Minor improvementExit 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.
| 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.