Guide for using Warden CLI locally to analyze code changes. Use when running warden commands, configuring warden.toml, creating custom skills, understanding triggers, or troubleshooting analysis issues. Triggers on "run warden", "warden config", "warden.toml", "create warden skill", "add trigger", or any Warden-related local development task.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Guide for using Warden CLI locally to analyze code changes. Use when running warden commands, configuring warden.toml, creating custom skills, understanding triggers, or troubleshooting analysis issues. Triggers on "run warden", "warden config", "warden.toml", "create warden skill", "add trigger", or any Warden-related local development task.
Warden Usage
Warden is an event-driven AI agent that analyzes code changes and executes configurable skills to produce structured reports with findings.
Quick Start
# Set API keyexport WARDEN_ANTHROPIC_API_KEY=sk-ant-...
# Analyze uncommitted changes (uses warden.toml triggers)
warden
# Run specific skill on uncommitted changes
warden --skill find-bugs
# Analyze specific files
warden src/auth.ts src/database.ts
# Analyze changes from git ref
warden main..HEAD
warden HEAD~3
CLI Reference
warden [command] [targets...] [options]
Commands:
(default) - Run analysis
init - Initialize warden.toml and GitHub workflow
add [skill] - Add skill trigger to warden.toml
sync [repo] - Update cached remote skills to latest
setup-app - Create GitHub App via manifest flow
Targets:
<files> - Specific files (e.g., src/auth.ts)
<glob> - Pattern match (e.g., src/**/*.ts)
<git-ref> - Git range (e.g., , )
main..HEAD
HEAD~3
(none) - Uncommitted changes
Key Options:
Option
Description
--skill <name>
Run only this skill
--config <path>
Path to warden.toml (default: ./warden.toml)
-m, --model <model>
Model to use
--json
Output as JSON
-o, --output <path>
Write output to JSONL file
--fail-on <severity>
Exit 1 if findings >= severity
--comment-on <severity>
Show findings >= severity
--fix
Auto-apply suggested fixes
--parallel <n>
Concurrent executions (default: 4)
--offline
Use cached remote skills only
-q, --quiet
Errors and summary only
-v, --verbose
Show real-time findings
-vv
Debug info (tokens, latency)
Severity levels:critical, high, medium, low, info, off
Skills live in .warden/skills/, .agents/skills/, or .claude/skills/.
Structure:
.warden/skills/my-skill/
└── SKILL.md
SKILL.md format:
---
name: my-skill
description: What this skill analyzes
allowed-tools: Read Grep Glob
---
[Analysis instructions for the agent]
## What to Look For- Specific issue type 1
- Specific issue type 2
## Output Format
Report findings with severity, location, and suggested fix.
Available tools:Read, Glob, Grep, WebFetch, WebSearch, Bash, Write, Edit
Remote Skills
Skills can be fetched from GitHub repositories:
# Add a remote skill
warden add --remote getsentry/skills --skill security-review
# Add with version pinning (recommended for reproducibility)
warden add --remote getsentry/skills@abc123 --skill security-review
# List skills in a remote repo
warden add --remote getsentry/skills --list
# Update all unpinned remote skills
warden sync# Update specific repo
warden sync getsentry/skills
# Run with cached skills only (no network)
warden --offline
