Skip to content
Skills Library
Programming · Review & audit

warden

/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.

Licence
MIT
Last repository change
22.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
5
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Triggers from the description

run wardencheck my changesreview before commitwarden configwarden.tomlcreate a warden skilladd trigger
Original author 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.

How it works

  1. References
  2. Running Warden
  3. Pre-Commit Workflow
  4. Reading Output
  5. Commands
Original SKILL.md headings · 73 lines, 303 words
SKILL.md preview
---
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 |
|----------|-----------|
| `${CLAUDE_SKILL_ROOT}/references/cli-reference.md` | Full option details, per-command flags, examples |
| `${CLAUDE_SKILL_ROOT}/references/configuration.md` | Editing warden.toml, triggers, patterns, troubleshooting |
| `${CLAUDE_SKILL_ROOT}/references/config-schema.md` | Exact field names, types, and defaults |
| `${CLAUDE_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_ANTHROPIC_API_KEY` or log in via `claude login` 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 `${CLAUDE_SKILL_ROOT}/references/cli-reference.md`.
Files in this package (5)
  • SKILL.md 2 KB
  • references/cli-reference.md 4 KB
  • references/config-schema.md 4 KB
  • references/configuration.md 3 KB
  • references/creating-skills.md 2 KB

Versions

RepositoryScoreLicence
This page · getsentry/xcodebuildmcp100MIT
seaworld008/commonly-used-high-value-skills100MIT
getsentry/warden100Apache-2.0

Identical content appears in 3 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version fd05ec80d68f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100warden-skill
    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…
  • 100warden-service
    Queries and summarizes the Warden Service read API. Use when asked to inspect, search, summarize, or export Warden runs, findings, costs, outcomes, repositories, skills, or memories through Warden Service.
  • 100warden-sweep
    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.
  • 100warden-sweep
    Full-repository code sweep. Scans every file with warden, verifies findings via 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.
  • 90warden-agent-builder
    Build original LangGraph agents for Warden Protocol and prepare them for publishing in Warden Studio. Use this skill when users want to: (1) Create new Warden agents (not community examples), (2) Build LangGraph-based crypto/Web3 agents, (3) Deploy agents via LangSmith…
  • 100upward-report
    Mandatory closing block for every warden response, and the input the parent routes on. Use when you are a warden finishing (or stopping) a mission, or when you are the parent reading a warden's result. The wardens SubagentStop hook sends the warden back once if the block is missing or invalid.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.