agentleFS
Sign inStart free
cameroncookecameroncooke/XcodeBuildMCP/.agents/skills/warden/SKILL.md

warden

Skill6.5k starsChanged 50 days agoMITView on GitHub

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.

  • Reads credentials

6 other projects use a version of this, 1 of them edited.

Trending

Quiet since May.about the whole repository

Dec 2025: 1 mentionJan 2026: 4 mentionsFeb 2026: 1 mentionMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the cameroncooke/XcodeBuildMCP repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about cameroncooke/XcodeBuildMCP

The biggest 5 of 21 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 21

Talked about on GitHub and Bluesky (21 times).

On GitHub · 17

12 more on GitHub

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run Warden to analyze code changes before committing.

    line 6
  2. Distinctive:

    Read the relevant reference when the task requires deeper detail:

    line 10
  3. Distinctive:

    After making code changes and before committing:

    line 46
  4. Very specific:

    Run warden to analyze uncommitted changes

    line 48
  5. Distinctive:

    Run Warden once to validate work.

    line 53

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Run Warden to analyze code changes before committing.

References

Read the relevant reference when the task requires deeper detail:

DocumentRead When
${CLAUDE_SKILL_ROOT}/references/cli-reference.mdFull option details, per-command flags, examples
${CLAUDE_SKILL_ROOT}/references/configuration.mdEditing warden.toml, triggers, patterns, troubleshooting
${CLAUDE_SKILL_ROOT}/references/config-schema.mdExact field names, types, and defaults
${CLAUDE_SKILL_ROOT}/references/creating-skills.mdWriting 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_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

CommandDescription
wardenRun analysis (default)
warden initInitialize warden.toml and GitHub workflow
warden add [skill]Add skill trigger to warden.toml
warden sync [remote]Update cached remote skills
warden setup-appCreate GitHub App via manifest flow

For full options and flags, read ${CLAUDE_SKILL_ROOT}/references/cli-reference.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free