SwissArmyHammer

SwissArmyHammer is an integrated software development lifecycle (SDLC) platform for AI-powered coding agents. It combines skills, agents, tools, and validators into a single system that turns your AI coding assistant into a complete development team.

Instead of a loose collection of scripts and prompts, SwissArmyHammer provides a structured composition of capabilities — each with a clear role — that work together to plan, implement, test, review, and ship code.

Three CLIs, One System

SwissArmyHammer ships as three complementary command-line tools:

Each tool is independently useful, but they’re designed to work together. sah provides the capabilities, avp enforces the guardrails, and mirdan lets you share and reuse everything.

How It Works

At its core, SwissArmyHammer extends AI coding agents (like Claude Code) with a composable set of SDLC primitives:

1. Skills define what to do — plan, implement, test, review, commit. Each skill is a self-contained workflow that the agent can invoke.
2. Agents (subagent modes) define how to think — a planner reasons differently than a tester. Agent modes shape the AI’s behavior for specific roles.
3. Tools provide what to work with — file operations, shell execution, code intelligence, kanban boards, git integration. These are the hands of the system.
4. Validators enforce what’s acceptable — code quality rules, security checks, test integrity. These run as hooks, catching problems before they land.

The agent orchestrates these pieces through a natural conversation interface. Say /plan and the system researches your codebase, decomposes work into kanban cards, and presents a plan. Say /implement and it picks up the next card, writes code, runs tests, and reports back. Say /review and a dedicated reviewer agent examines the changes with language-specific guidelines.

The SDLC Loop

A typical development cycle with SwissArmyHammer looks like:

/plan  →  /implement  →  /test  →  /review  →  /commit
  ↑                                                |
  └────────────────────────────────────────────────┘

Each step is a skill backed by specialized agent modes and tools. The kanban board tracks progress across steps. Validators run continuously in the background, enforcing quality at every stage.

This isn’t a rigid pipeline — you can use any skill independently, skip steps, or run them in any order. The system is designed to support how developers actually work, not to impose a process.

What Makes It Different

• Composition over configuration. Skills, agents, tools, and validators are separate, pluggable units. Mix and match what you need.
• Agent-native. Built from the ground up as an MCP server for AI coding agents, not retrofitted from human-oriented tooling.
• Quality built in. Validators run as hooks on every tool call — code quality, security, and test integrity are enforced automatically, not as an afterthought.
• Shareable. Mirdan provides a package registry so teams can publish and install skills, validators, tools, and plugins. Your team’s best practices become installable packages.
• Language-aware. Review guidelines, coverage analysis, and code intelligence adapt to the language you’re working in — Rust, TypeScript, Python, Go, and more.

The Integrated SDLC

SwissArmyHammer assembles four kinds of building blocks — skills, agents, tools, and validators — into a coherent software development lifecycle. This page explains how they fit together.

The Four Layers

┌─────────────────────────────────────────────┐
│                  Skills                      │
│   /plan  /implement  /test  /review /commit  │
│         (what to do — workflows)             │
├─────────────────────────────────────────────┤
│                  Agents                      │
│   planner  implementer  tester  reviewer     │
│         (how to think — personas)            │
├─────────────────────────────────────────────┤
│                  Tools                       │
│   files  shell  git  kanban  code-context    │
│         (what to work with — capabilities)   │
├─────────────────────────────────────────────┤
│                Validators                    │
│   code-quality  security  test-integrity     │
│         (what's acceptable — guardrails)     │
└─────────────────────────────────────────────┘

Each layer has a distinct responsibility, and the layers compose vertically. A skill like /implement activates the implementer agent mode, which uses tools (file editing, shell execution, code context) to write code, while validators (code quality, security rules) check every change as it happens.

A Concrete Example

Here’s what happens when you type /plan in your AI coding agent:

1. The plan skill activates. It defines the workflow: research the codebase, identify what needs to change, decompose work into discrete tasks.
2. The planner agent mode shapes how the AI thinks. It’s instructed to be thorough in research, conservative in scope, and to produce kanban cards as output.
3. The planner uses tools to do the work: code_context to understand the codebase structure, shell to run analysis commands, kanban to create task cards, question to ask clarifying questions.
4. Validators aren’t heavily involved during planning, but command-safety validators still ensure no destructive shell commands are run during research.

The result: a kanban board with well-scoped cards, ready for /implement to pick up.

The Development Cycle

The skills form a natural development cycle:

Plan → Implement → Test → Review → Commit

Each phase is independent — you can run /test without /plan, or /review without /implement. But when used together, they form a complete cycle where each phase’s output feeds the next.

Supporting Skills

Beyond the core cycle, additional skills handle cross-cutting concerns:

• /coverage — analyzes test coverage gaps on changed code
• /deduplicate — finds and refactors duplicate code
• /double-check — validates recent work before moving on
• /implement-all — autonomously works through the entire kanban board
• /code-context — explores codebase structure and symbol relationships
• /shell — shell command execution with history and process management
• /lsp — diagnoses and installs language servers for code intelligence

How the Pieces Connect

Skills Activate Agent Modes

When a skill runs, it typically delegates to a specialized subagent. The /implement skill spawns an implementer agent, the /review skill spawns a reviewer agent, and so on. This keeps the parent conversation clean — verbose test output, detailed code analysis, and implementation details stay inside the subagent.

Agent Modes Shape Behavior

Each agent mode is a markdown document that instructs the AI how to approach its task. The implementer follows test-driven development practices, writes minimal diffs, and reports results. The reviewer performs layered analysis (correctness, design, style) with language-specific guidelines. These aren’t just prompts — they’re behavioral contracts.

Tools Provide Capabilities

Tools are MCP (Model Context Protocol) endpoints that the agent calls to interact with the outside world. File operations, shell execution, code intelligence, kanban management — these are all tools. Skills and agents don’t hard-code tool usage; they decide which tools to use based on the task at hand.

Validators Run Continuously

Validators are Claude Code hooks that fire on every tool call. When the agent writes a file, the code-quality validator checks for cognitive complexity, magic numbers, and naming issues. When it runs a shell command, the command-safety validator ensures it’s not destructive. This happens transparently — the agent gets feedback and can self-correct before problems land.

Extensibility

Every layer is extensible:

• Skills are markdown files. Drop a new one into .claude/skills/ or install one via mirdan install.
• Agent modes are markdown files in the modes directory. Customize existing ones or create new specialized roles.
• Tools are MCP server endpoints. SwissArmyHammer’s built-in tools cover the common cases; add more via MCP server configuration.
• Validators are AVP rule sets. Create project-specific rules with avp new or install shared ones via mirdan install.

The package manager (mirdan) ties extensibility to shareability — anything you create can be published to a registry and installed by others.

Skills

Skills are the workflows of SwissArmyHammer. Each skill defines a specific development activity — planning, implementing, testing, reviewing, committing — as a self-contained unit that the AI agent can invoke.

What a Skill Is

A skill is a markdown file with frontmatter metadata. When invoked (e.g., /plan or /implement), it expands into a full prompt that shapes the agent’s behavior for that activity. Skills typically delegate heavy work to specialized subagents, keeping the parent conversation concise.

Skills are the primary interface between you and the SDLC system. You don’t need to think about agents, tools, or validators directly — just invoke the skill and it orchestrates everything.

Built-in Skills

SwissArmyHammer ships with skills covering the core development cycle:

How Skills Work

When you type /implement, here’s what happens:

1. The skill definition is loaded and expanded into a prompt.
2. The prompt typically instructs the agent to delegate to a specialized subagent (the implementer agent mode).
3. The subagent does the work — reading code, writing files, running tests — using tools.
4. Validators check the subagent’s work as it happens.
5. The subagent reports results back to the parent conversation.

This delegation pattern keeps verbose output (test results, implementation details) contained in the subagent, while the parent conversation gets a clean summary.

Installing Skills

Beyond the built-in set, you can install additional skills from the Mirdan registry:

mirdan search "my-skill"
mirdan install my-skill

Or create your own by placing a SKILL.md file in the appropriate directory. Skills installed via Mirdan are deployed to each detected agent’s skill directory automatically.

Skill Locations

Skills are discovered from multiple locations with hierarchical precedence:

Agents

Agents are specialized behavioral modes that shape how the AI approaches a task. When a skill needs to plan, implement, test, or review, it spawns a subagent with the appropriate mode — giving it a focused persona and set of instructions for that specific role.

What an Agent Mode Is

An agent mode is a markdown document that defines a role. It tells the AI:

• What its job is (implement code, review changes, run tests)
• How to approach the work (test-driven development, layered review, minimal diffs)
• What patterns to follow (commit conventions, error handling, reporting format)
• What tools to prefer and how to use them

Agent modes aren’t just system prompts — they’re behavioral contracts that ensure consistent, high-quality output regardless of the specific task.

Built-in Agent Modes

The Subagent Pattern

Skills typically don’t do work directly in the parent conversation. Instead, they delegate to a subagent:

Parent conversation
  │
  ├─ /implement
  │    └─ spawns implementer subagent
  │         ├─ reads kanban card
  │         ├─ writes code (using file tools)
  │         ├─ runs tests (using shell tool)
  │         ├─ validators check each change
  │         └─ reports results back to parent
  │
  └─ "Implementation complete, all tests passing"

This pattern has two key benefits:

1. Context isolation. Verbose output (test results, file contents, tool calls) stays inside the subagent. The parent conversation gets a clean summary.
2. Focused behavior. Each subagent operates with instructions optimized for its specific role, without the noise of unrelated context.

How Modes Shape Behavior

Consider the difference between the implementer and reviewer modes:

The implementer is instructed to:

• Follow test-driven development (write failing test first, then make it pass)
• Make minimal changes — only what the kanban card requires
• Run tests after every change
• Report what was changed and whether tests pass

The reviewer is instructed to:

• Perform layered analysis: correctness first, then design, then style
• Apply language-specific review guidelines (Rust, TypeScript, Python, etc.)
• Capture findings as kanban cards for follow-up
• Never modify code directly — only report findings

Same tools, completely different behavior. The agent mode is what makes the difference.

Language-Specific Guidelines

Some agent modes include language-specific guidelines that activate based on the code being worked with. The reviewer, for example, loads additional guidelines for:

• Rust — ownership patterns, error handling, unsafe usage
• TypeScript/JavaScript — type safety, async patterns, React conventions
• Python — type hints, exception handling, import organization
• Go — error handling, goroutine safety, interface design
• Dart/Flutter — widget patterns, state management

These guidelines are bundled as partials within the skill definition and selected automatically based on the files being reviewed.

Tools

Tools are the capabilities that agents use to interact with the outside world. They’re exposed as MCP (Model Context Protocol) endpoints — the agent calls them like functions to read files, run commands, search code, manage tasks, and more.

What a Tool Is

A tool is an MCP endpoint with a defined schema (name, description, parameters) and an implementation. When the agent decides it needs to read a file or run a shell command, it invokes the appropriate tool. SwissArmyHammer’s MCP server (sah serve) exposes all built-in tools to the connected agent.

Tools are the lowest layer of the system. Skills and agents don’t hard-code which tools to use — they make decisions based on the task and invoke tools as needed.

Built-in Tools

File Operations

Execution

Code Intelligence

Project Management

Git

Communication

Agent Orchestration

Web

How Tools Fit In

Tools sit beneath skills and agents in the stack. Here’s the relationship:

• A skill (e.g., /test) defines the workflow.
• An agent mode (e.g., tester) shapes how the AI approaches the task.
• Tools (e.g., shell, files) are what the agent actually calls to do the work.
• Validators (e.g., command-safety) check each tool invocation before it executes.

The agent has access to all tools and chooses which to use based on context. The skill and agent mode influence these choices through their instructions, but tools themselves are general-purpose.

MCP Protocol

All tools are served via the Model Context Protocol. When you run sah serve, it starts an MCP server (stdio by default, HTTP optionally) that exposes these tools to any connected agent. Claude Code discovers them automatically via the MCP configuration created by sah init.

This means SwissArmyHammer’s tools work alongside any other MCP servers you have configured. The agent sees a unified tool palette from all sources.

Validators

Validators are the guardrails of SwissArmyHammer. They run as Claude Code hooks — firing on every tool call — to enforce code quality, security, and test integrity automatically. Instead of catching problems in review, validators prevent them from being introduced in the first place.

What a Validator Is

A validator is an AVP (Agent Validator Protocol) rule set: a collection of rules organized under a VALIDATOR.md file. Each rule is a markdown document that describes what to check and how to report violations. AVP processes these rules against the agent’s tool calls and file changes in real time.

Built-in Validators

SwissArmyHammer ships with four validator sets:

Code Quality

Enforces structural code quality rules:

• Cognitive complexity — flags overly complex functions
• Function length — catches functions that are too long
• Naming consistency — enforces naming conventions
• No commented-out code — prevents dead code from accumulating
• No hard-coded values — catches embedded credentials and config
• No magic numbers — requires named constants
• No string equality — flags fragile string comparisons
• No log truncation — ensures complete error logging
• Missing docs — flags undocumented public APIs

Security Rules

Catches security vulnerabilities:

• Input validation — ensures user input is validated at boundaries
• No secrets — prevents credentials, tokens, and keys from being committed

Command Safety

Guards against destructive shell commands:

• Safe commands — blocks rm -rf /, DROP TABLE, force pushes, and other dangerous operations

Test Integrity

Prevents test cheating:

• No test cheating — catches mocking of the thing under test, assertion-free tests, and other patterns that make tests pass without testing anything

How Validators Work

Validators run as hooks in Claude Code’s hook system. When the agent makes a tool call (writing a file, running a command), AVP intercepts it and runs the relevant validators:

Agent calls tool (e.g., write file)
    │
    ├─ AVP hook fires
    │    ├─ Code quality validator checks the change
    │    ├─ Security validator checks for secrets
    │    └─ Results fed back to agent
    │
    └─ Agent sees feedback, can self-correct

This happens transparently. The agent doesn’t need to explicitly invoke validators — they run automatically on every relevant action.

Setting Up Validators

Install AVP hooks into your project:

avp init

This registers AVP as a Claude Code hook and creates the .avp/ directory. Built-in validators are always available; project-specific validators go in .avp/validators/.

Creating Custom Validators

Create a new validator rule set:

avp new my-rules

This scaffolds a validator with a VALIDATOR.md and rules/ directory. Each rule is a markdown file describing what to check.

Sharing Validators

Validators can be published and installed via Mirdan:

# Create and publish
mirdan new validator my-team-rules
mirdan publish

# Install on another project
mirdan install my-team-rules

This lets teams codify their standards as installable packages — new projects get the team’s quality rules with a single command.

Validator Locations

Installation

Install SwissArmyHammer and configure it for use with Claude Code.

Prerequisites

• Claude Code — For MCP integration (recommended)
• Git — For version control features

Install from Homebrew

brew install swissarmyhammer/tap/swissarmyhammer-cli

This installs all three CLIs: sah, avp, and mirdan.

Verify Installation

sah --version
sah doctor

The doctor command checks your installation and configuration.

Claude Code Integration

Initialize SwissArmyHammer for your project:

sah init

This does two things:

1. Registers sah as an MCP server in .mcp.json
2. Creates the project directory with skills and workflows

Set up validators:

avp init

This registers AVP hooks in Claude Code settings and creates the .avp/ directory.

Verify everything:

sah doctor
avp doctor

Scope Options

Both sah init and avp init support different scopes:

sah init user      # Install globally
avp init user      # Install hooks globally

Shell Completions (Optional)

# Zsh
sah completions zsh > ~/.zfunc/_sah

# Bash
sah completions bash > ~/.bash_completion.d/sah

# Fish
sah completions fish > ~/.config/fish/completions/sah.fish

Next Steps

• Quick Start — Start using the integrated SDLC

Quick Start

Get the integrated SDLC running in your project.

Setup

# Install
brew install swissarmyhammer/tap/swissarmyhammer-cli

# Initialize in your project
cd your-project
sah init        # MCP server + tools + skills
avp init        # Validators (hooks)

# Verify
sah doctor
avp doctor

The Development Cycle

Once initialized, the skills are available as slash commands in Claude Code:

1. Plan

/plan

Researches your codebase and creates kanban cards for the work ahead. The planner agent explores code structure, identifies dependencies, and decomposes the task into implementable units.

2. Implement

/implement

Picks up the next kanban card and implements it. The implementer agent writes code, runs tests, and reports results. Validators check every file write for code quality and security issues.

To work through the entire board autonomously:

/implement-all

3. Test

/test

Runs the test suite, analyzes failures, fixes issues, and reports back. The tester agent handles verbose test output so your conversation stays clean.

4. Review

/review

Performs a structured code review of your changes. The reviewer agent applies language-specific guidelines and captures findings.

5. Commit

/commit

Creates clean, well-organized git commits from your staged changes.

Other Useful Skills

/coverage          # Find untested code in your changes
/deduplicate       # Find and refactor copy-paste code
/double-check      # Verify recent work before moving on
/code-context      # Explore codebase structure
/shell             # Run shell commands with history

Installing More Skills

Browse and install community skills via Mirdan:

mirdan search "my-topic"
mirdan install some-skill

Next Steps

• The Integrated SDLC — Understand how skills, agents, tools, and validators work together
• Skills — Deep dive into the skill system
• Validators — Configure quality guardrails

Command-Line Help for swissarmyhammer

This document contains the help content for the swissarmyhammer command-line program.

Installation

brew install swissarmyhammer/tap/swissarmyhammer

Command Overview:

• swissarmyhammer↴
• swissarmyhammer serve↴
• swissarmyhammer serve http↴
• swissarmyhammer init↴
• swissarmyhammer deinit↴
• swissarmyhammer doctor↴
• swissarmyhammer prompt↴
• swissarmyhammer flow↴
• swissarmyhammer completion↴
• swissarmyhammer validate↴
• swissarmyhammer model↴
• swissarmyhammer model list↴
• swissarmyhammer model show↴
• swissarmyhammer model use↴
• swissarmyhammer agent↴
• swissarmyhammer agent acp↴

swissarmyhammer

swissarmyhammer is an MCP (Model Context Protocol) server that manages prompts as markdown files. It supports file watching, template substitution, and seamless integration with Claude Code.

Global arguments can be used with any command to control output and behavior: –verbose Show detailed information and debug output –format Set output format (table, json, yaml) for commands that support it
–debug Enable debug mode with comprehensive tracing –quiet Suppress all output except errors –model Override model for all use cases (runtime only, doesn’t modify config)

Main commands: serve Run as MCP server (default when invoked via stdio) doctor Diagnose configuration and setup issues prompt Manage and test prompts with interactive capabilities flow Execute and manage workflows for complex task automation agent Manage and interact with specialized agents for specific use cases validate Validate prompt files and workflows for syntax and best practices completion Generate shell completion scripts

Example usage: swissarmyhammer serve # Run as MCP server swissarmyhammer doctor # Check configuration swissarmyhammer –verbose prompt list # List prompts with details swissarmyhammer –format=json prompt list # List prompts as JSON swissarmyhammer –debug prompt test help # Test prompt with debug info swissarmyhammer agent list # List available agents swissarmyhammer agent use claude-code # Apply Claude Code agent to project swissarmyhammer flow run code-review # Execute code review workflow

Usage: swissarmyhammer [OPTIONS] [COMMAND]

Subcommands:

• serve — Run as MCP server (default when invoked via stdio)
• init — Initialize sah MCP server in Claude Code settings
• deinit — Remove sah MCP server from Claude Code settings
• doctor — Diagnose configuration and setup issues
• prompt — Manage and test prompts
• flow — Execute and manage workflows
• completion — Generate shell completion scripts
• validate — Validate prompt files and workflows for syntax and best practices
• model — Manage and interact with models
• agent — Manage and interact with Agent Client Protocol server

Options:

• -v, --verbose — Enable verbose logging

• -d, --debug — Enable debug logging

• -q, --quiet — Suppress all output except errors

• --format <FORMAT> — Global output format

  Possible values: table, json, yaml

• --model <MODEL> — Override model for all use cases (runtime only, doesn’t modify config)

swissarmyhammer serve

Run as MCP server. This is the default mode when invoked via stdio (e.g., by Claude Code). The server will:

• Load all prompts from builtin, user, and local directories
• Watch for file changes and reload prompts automatically
• Expose prompts via the MCP protocol
• Support template substitution with {{variables}}

Example: swissarmyhammer serve # Stdio mode (default) swissarmyhammer serve http # HTTP mode

Or configure in Claude Code’s MCP settings

Usage: swissarmyhammer serve [COMMAND]

Subcommands:

• http — Start HTTP MCP server

swissarmyhammer serve http

Start HTTP MCP server for web clients, debugging, and LlamaAgent integration. The server exposes MCP tools through HTTP endpoints and provides:

• RESTful MCP protocol implementation
• Health check endpoint at /health
• Support for random port allocation (use port 0)
• Graceful shutdown with Ctrl+C

Example: swissarmyhammer serve http –port 8080 –host 127.0.0.1 swissarmyhammer serve http –port 0 # Random port

Usage: swissarmyhammer serve http [OPTIONS]

Options:

• -p, --port <PORT> — Port to bind to (use 0 for random port)

  Default value: 8000

• -H, --host <HOST> — Host to bind to

  Default value: 127.0.0.1

swissarmyhammer init

Initialize SwissArmyHammer for use with Claude Code.

This command:

1. Registers sah as an MCP server in Claude Code settings
2. Creates the .sah/ project directory (workflows/) and .prompts/

The command is idempotent - safe to run multiple times.

Targets: project Write to .mcp.json (default, shared with team via git) local Write to ~/.claude.json per-project config (personal, not committed) user Write to ~/.claude.json global config (all projects)

Examples: sah init # Project-level setup (default) sah init user # Global setup for all projects sah init local # Personal setup, not committed to git

Usage: swissarmyhammer init [TARGET]

Arguments:

• <TARGET> — Where to install the MCP server configuration

  Default value: project

  Possible values:

  • project: Project-level settings (.claude/settings.json)
  • local: Local project settings, not committed (.claude/settings.local.json)
  • user: User-level settings (~/.claude/settings.json)

swissarmyhammer deinit

Remove SwissArmyHammer MCP server configuration from Claude Code settings.

By default, only the MCP server entry is removed from the settings file. Use –remove-directory to also delete the .sah/ project directory.

Examples: sah deinit # Remove from project settings sah deinit user # Remove from user settings sah deinit –remove-directory # Also remove .sah/

Usage: swissarmyhammer deinit [OPTIONS] [TARGET]

Arguments:

• <TARGET> — Where to remove the MCP server configuration from

  Default value: project

  Possible values:

  • project: Project-level settings (.claude/settings.json)
  • local: Local project settings, not committed (.claude/settings.local.json)
  • user: User-level settings (~/.claude/settings.json)

Options:

• --remove-directory — Also remove .sah/ project directory

swissarmyhammer doctor

Diagnose and troubleshoot your SwissArmyHammer setup in seconds.

Save hours of debugging time with comprehensive automated checks that identify configuration issues, permission problems, and integration errors before they impact your workflow.

WHAT IT CHECKS

The doctor command runs a complete health assessment of your environment: • PATH Configuration - Verifies swissarmyhammer is accessible from your shell • Claude Code Integration - Validates MCP server configuration and connectivity • Prompt System - Checks directories, file permissions, and YAML syntax • File Watching - Tests file system event monitoring capabilities • System Resources - Validates required dependencies and system capabilities

WHY USE DOCTOR

• Quick Diagnosis - Complete system check in seconds, not hours • Clear Reporting - Easy-to-understand pass/fail results with actionable guidance • Early Detection - Catch configuration problems before they cause failures • Setup Validation - Verify your installation is working correctly • Integration Testing - Ensure Claude Code and MCP are properly connected

UNDERSTANDING RESULTS

Exit codes indicate the severity of findings: 0 - All checks passed - System is healthy and ready 1 - Warnings found - System works but has recommendations 2 - Errors found - Critical issues preventing proper operation

COMMON WORKFLOWS

First-time setup verification: swissarmyhammer doctor

Detailed diagnostic output: swissarmyhammer doctor –verbose

After configuration changes: swissarmyhammer doctor

CI/CD health checks: swissarmyhammer doctor && echo “System ready”

EXAMPLES

Basic health check: swissarmyhammer doctor

Detailed diagnostics with fix suggestions: swissarmyhammer doctor –verbose

Quiet mode for scripting: swissarmyhammer doctor –quiet

The doctor command gives you confidence that your development environment is properly configured and ready for AI-powered workflows.

Usage: swissarmyhammer doctor

swissarmyhammer prompt

Manage and test prompts with a clean, simplified interface.

The prompt system provides two main commands: • list - Display all available prompts from all sources
• test - Test prompts interactively with sample data

Use global arguments to control output: –verbose Show detailed information –format FORMAT Output format: table, json, yaml –debug Enable debug mode –quiet Suppress output except errors

Examples: sah prompt list # List all prompts sah –verbose prompt list # Show detailed information sah –format=json prompt list # Output as JSON sah prompt test code-review # Interactive testing sah prompt test help –var topic=git # Test with parameters
sah –debug prompt test plan # Test with debug output

Usage: swissarmyhammer prompt [ARGS]...

Arguments:

• <ARGS> — Subcommand and arguments for prompt (handled dynamically)

swissarmyhammer flow

Automate complex development workflows with powerful, resumable state machines.

Workflows orchestrate multi-step processes including code reviews, deployments, testing, and AI-powered operations. Define once, run reliably, resume anywhere.

WORKFLOW POWER

State Machine Architecture: • Define complex processes as declarative state machines • Execute actions, tools, and AI commands in sequence or parallel • Handle conditional logic, loops, and error recovery • Resume interrupted workflows exactly where they stopped • Track execution state, variables, and progress

Built for Reliability: • Pause and resume workflows without losing state • Interactive mode for step-by-step control and debugging • Dry-run mode to preview execution without side effects • Comprehensive logging and status tracking • Automatic error handling and recovery options

AI Integration: • Execute Claude commands within workflow steps • Pass variables and context between AI operations • Chain AI-powered analysis, planning, and implementation • Combine automated and AI-assisted tasks seamlessly

COMMANDS

The flow system provides comprehensive workflow management:

• run - Start a new workflow execution with variables • resume - Continue a paused or interrupted workflow run • list - Display all available workflows from all sources • status - Check execution state and progress of a run • logs - View detailed execution logs and step history

WORKFLOW DISCOVERY

Workflows are loaded from multiple sources: • Built-in workflows - Standard development workflows included • User workflows (~/.sah/workflows/) - Personal automations • Project workflows (./workflows/) - Project-specific processes

COMMON WORKFLOWS

Start a workflow with parameters: swissarmyhammer flow run code-review –vars file=main.rs

Preview execution without running: swissarmyhammer flow run deploy –dry-run

Resume after interruption: swissarmyhammer flow resume a1b2c3d4

Interactive step-through debugging: swissarmyhammer flow resume a1b2c3d4 –interactive

Monitor workflow status: swissarmyhammer flow status a1b2c3d4 –watch

View execution history: swissarmyhammer flow logs a1b2c3d4

List available workflows: swissarmyhammer flow list –format json

EXECUTION OPTIONS

Pass variables to workflows: –vars key=value # Single variable –vars file=main.rs –vars author=jane # Multiple variables

Control execution: –interactive # Step-by-step confirmation –dry-run # Show plan without executing

EXAMPLES

Run code review workflow: swissarmyhammer flow run code-review –vars file=main.rs –vars severity=high

Test deployment workflow: swissarmyhammer flow run deploy –dry-run

Resume interrupted workflow: swissarmyhammer flow resume a1b2c3d4 –interactive

Check workflow status: swissarmyhammer flow status a1b2c3d4

View execution logs: swissarmyhammer flow logs a1b2c3d4 –format json

List available workflows: swissarmyhammer flow list

Workflows bring automation, reliability, and AI-powered intelligence to your development processes. Define complex operations once and execute them consistently every time.

Usage: swissarmyhammer flow [ARGS]...

Arguments:

• <ARGS> — Workflow name or ‘list’ command followed by arguments

swissarmyhammer completion

Generates shell completion scripts for various shells. Supports:

• bash
• zsh
• fish
• powershell

Examples:

Bash (add to ~/.bashrc or ~/.bash_profile)

swissarmyhammer completion bash > ~/.local/share/bash-completion/completions/swissarmyhammer

Zsh (add to ~/.zshrc or a file in fpath)

swissarmyhammer completion zsh > ~/.zfunc/_swissarmyhammer

Fish

swissarmyhammer completion fish > ~/.config/fish/completions/swissarmyhammer.fish

PowerShell

swissarmyhammer completion powershell >> $PROFILE

Usage: swissarmyhammer completion <SHELL>

Arguments:

• <SHELL> — Shell to generate completion for

  Possible values: bash, elvish, fish, powershell, zsh

swissarmyhammer validate

Catch configuration errors before they cause failures with comprehensive validation.

The validate command ensures quality and correctness across your entire SwissArmyHammer configuration, detecting syntax errors, structural issues, and best practice violations before they impact your workflows.

Quality Assurance

Comprehensive Validation: • Prompt files from all sources (builtin, user, project) • Workflow definitions from standard locations • MCP tool schemas and CLI integration (with –validate-tools) • Template syntax and variable usage • YAML frontmatter structure • Required field presence and format • Best practice compliance

Early Error Detection: • Find syntax errors before execution • Identify missing required fields • Detect template variable mismatches • Validate workflow state machine structure • Check MCP tool schema correctness • Verify CLI integration compatibility

CI/CD Integration: • Automated quality checks in build pipelines • Exit codes indicate validation results • Quiet mode for clean CI output • JSON output for tool integration • Fast execution for rapid feedback

What Gets Validated

Prompt Files: • YAML frontmatter syntax correctness • Required fields: title, description • Template variable declarations match usage • Liquid template syntax validity • Parameter definitions and types • Default value correctness • Partial marker handling

Workflow Files: • State machine structure integrity • State connectivity and transitions • Action and tool references • Variable declarations and usage • Conditional logic syntax • Loop and iteration constructs • Error handling configuration

MCP Tools (with –validate-tools): • JSON schema correctness • Parameter type definitions • Required vs optional field specifications • Tool description completeness • CLI integration requirements • Documentation quality • Best practice adherence

Validation Modes

Standard validation (prompts and workflows):

sah validate

Comprehensive validation (including MCP tools):

sah validate --validate-tools

CI/CD mode (errors only, no warnings):

sah validate --quiet
sah validate --validate-tools --quiet

Machine-readable output:

sah validate --format json
sah validate --validate-tools --format json

Exit Codes

• 0 - All validation passed, no errors or warnings
• 1 - Warnings found but no errors
• 2 - Errors found that require fixes

Use exit codes in scripts and CI pipelines:

sah validate || exit 1

Discovery and Sources

Prompts validated from: • Built-in prompts (embedded in binary) • User prompts (~/.prompts/) • Project prompts (./.prompts/)

Workflows validated from: • Built-in workflows (embedded in binary) • User workflows (~/.sah/workflows/) • Project workflows (./workflows/)

MCP tools validated from: • SwissArmyHammer tool definitions • CLI command integration points • Tool parameter schemas

Common Use Cases

Pre-commit validation:

sah validate --quiet && git commit

CI pipeline check:

sah validate --validate-tools --format json > validation-report.json

Development workflow validation:

sah validate --verbose

Quality gate in deployment:

sah validate --validate-tools --quiet || exit 1

Validation Checks

YAML Frontmatter: • Syntax correctness • Required fields present • Field types match expectations • Valid enum values

Template Syntax: • Liquid template parsing • Variable references exist • Filter syntax correctness • Control flow validity • Partial references resolve

Workflow Structure: • All states are reachable • Transitions are valid • Actions reference existing tools • Variables are declared before use • Error handlers are properly configured

MCP Tool Schemas: • JSON schema validity • Parameter type correctness • Required field specification • Tool description quality • CLI integration completeness

Best Practices: • Descriptive titles and descriptions • Proper parameter documentation • Sensible default values • Clear error messages • Consistent naming conventions

Examples

Basic validation:

sah validate

Full system validation:

sah validate --validate-tools

Quiet mode for CI:

sah validate --quiet

Detailed output:

sah --verbose validate

JSON output for tooling:

sah validate --format json | jq '.errors'

Validate after changes:

sah validate --validate-tools --verbose

Output Formats

Table format (default): • Human-readable tabular output • Color-coded error/warning levels • File paths and line numbers • Clear error descriptions

JSON format: • Machine-parseable structured output • Complete error and warning details • Suitable for CI integration • Easy tool consumption

YAML format: • Human-readable structured output • Hierarchical error organization • Good for documentation • Easy diff comparison

Troubleshooting

Validation errors in prompts: • Check YAML frontmatter syntax • Verify all required fields present • Ensure template variables declared • Test Liquid template syntax

Validation errors in workflows: • Verify state machine structure • Check all state transitions • Ensure action references valid • Validate variable declarations

Validation errors in tools: • Review JSON schema correctness • Check parameter type definitions • Verify required fields specified • Ensure documentation complete

Integration with Development Workflow

Pre-commit hook:

#!/bin/bash
sah validate --quiet || {
  echo "Validation failed. Fix errors before committing."
  exit 1
}

Git hook (.git/hooks/pre-commit):

#!/bin/bash
sah validate --validate-tools --quiet

Make target:

validate:
	sah validate --validate-tools --quiet

.PHONY: validate

CI pipeline (GitHub Actions):

- name: Validate Configuration
  run: sah validate --validate-tools --format json

Benefits

Catch Errors Early: • Find problems before runtime • Prevent workflow failures • Avoid wasted execution time • Reduce debugging effort

Ensure Quality: • Enforce best practices • Maintain consistent standards • Improve documentation quality • Promote good patterns

Enable Confidence: • Deploy with certainty • Refactor safely • Share configuration reliably • Integrate automatically

Support Automation: • CI/CD quality gates • Automated testing • Pre-commit validation • Continuous quality monitoring

The validate command is your quality assurance system for SwissArmyHammer configuration, ensuring that prompts, workflows, and tools are correct, complete, and ready for reliable operation.

Usage: swissarmyhammer validate [OPTIONS]

Options:

• -q, --quiet — Suppress all output except errors. In quiet mode, warnings are hidden from both output and summary

• --format <FORMAT> — Output format

  Default value: table

  Possible values: table, json, yaml

• --validate-tools — Validate MCP tool schemas for CLI compatibility

swissarmyhammer model

Manage and interact with models in the SwissArmyHammer system.

Models provide specialized AI execution environments and configurations for specific development workflows. They enable you to switch between different AI models, execution contexts, and toolchains based on your project’s needs.

MODEL DISCOVERY AND PRECEDENCE

Models are loaded from multiple sources with hierarchical precedence: • Built-in models (lowest precedence) - Embedded in the binary • Project models (medium precedence) - ./models/.yaml in your project • User models (highest precedence) - ~/.models/.yaml

Higher precedence models override lower ones by name. This allows you to customize built-in models or create project-specific variants.

BUILT-IN MODELS

The system includes these built-in models: • claude-code - Default Claude Code integration with shell execution • qwen-coder - Local Qwen3-Coder model with in-process execution

COMMANDS

The model system provides two main commands: • list - Display all available models from all sources with descriptions • use - Apply a model configuration to the current project

When you ‘use’ a model, it creates or updates .sah/sah.yaml in your project with the model’s configuration. This configures how SwissArmyHammer executes AI workflows in your project.

COMMON WORKFLOWS

1. Explore available models: sah model list

2. Apply a model to your project: sah model use claude-code

3. Switch to a different model: sah model use qwen-coder

4. View detailed model information: sah –verbose model list

Use global arguments to control output: –verbose Show detailed information and descriptions –format FORMAT Output format: table, json, yaml –debug Enable debug mode with comprehensive tracing –quiet Suppress output except errors

Examples: sah model list # List all available models sah –verbose model list # Show detailed information and descriptions sah –format=json model list # Output as structured JSON sah model use claude-code # Apply Claude Code model to project sah model use qwen-coder # Switch to local Qwen3-Coder model sah –debug model use custom-model # Apply model with debug output

CUSTOMIZATION

Create custom models by adding .yaml files to: • ./models/ (project-specific models) • ~/.models/ (user-wide models)

Custom models can override built-in models by using the same name, or provide entirely new configurations for specialized workflows.

Usage: swissarmyhammer model [COMMAND]

Subcommands:

• list — List available models
• show — Show current model use case assignments
• use — Use a specific model

swissarmyhammer model list

List all available models from built-in, project, and user sources.

Models are discovered with hierarchical precedence where user models override project models, which override built-in models. This command shows all available models with their sources and descriptions.

Built-in models are embedded in the binary and provide default configurations for common workflows. Project models (./models/.yaml) allow customization for specific projects. User models (~/.models/.yaml) provide personal configurations that apply across all projects.

Output includes: • Model name and source (built-in, project, or user) • Description when available • Current model status (if one is applied to the project)

Examples: sah model list # List all models in table format sah model list –format json # Output as JSON for processing sah –verbose model list # Include detailed descriptions sah –quiet model list # Only show model names

Usage: swissarmyhammer model list [OPTIONS]

Options:

• --format <FORMAT> — Output format

  Default value: table

  Possible values: table, json, yaml

swissarmyhammer model show

Display current model use case assignments showing which model is configured for each use case in the project.

SwissArmyHammer supports configuring different models for different use cases: • root - Default model for general operations • workflows - Model for workflow execution (plan, review, implement, etc.)

This command shows the current assignment for each use case, including whether the assignment comes from explicit configuration or falls back to the root model.

Examples: sah model show # Show use case assignments sah model # Same as ‘show’ (default)

Usage: swissarmyhammer model show [OPTIONS]

Options:

• --format <FORMAT> — Output format

  Default value: table

  Possible values: table, json, yaml

swissarmyhammer model use

Apply a specific model configuration to the current project or for a specific use case.

This command finds the specified model by name and applies its configuration to the project by creating or updating .sah/sah.yaml. The model configuration determines how SwissArmyHammer executes AI workflows in your project, including which AI model to use and how to execute tools.

SwissArmyHammer supports configuring different models for different use cases: • root - Default model for general operations (default when use case not specified) • workflows - Model for workflow execution (plan, review, implement, etc.)

Model precedence (highest to lowest): • User models: ~/.models/.yaml • Project models: ./models/.yaml • Built-in models: embedded in the binary

The command preserves any existing configuration sections while updating only the model configuration. This allows you to maintain project-specific settings alongside model configurations.

Common model types: • claude-code - Uses Claude Code CLI for AI execution • qwen-coder - Uses local Qwen3-Coder model with in-process execution • custom models - User-defined configurations for specialized workflows

Examples: sah model use claude-code # Apply Claude Code model to root use case sah model use root claude-code # Apply Claude Code model to root use case (explicit) sah model use workflows claude-code # Apply Claude Code to workflows use case sah –debug model use claude-code # Apply with debug output

Usage: swissarmyhammer model use <first> [second]

Arguments:

• <first> — First argument: either model name (sets root) OR use case (root, workflows)
• <second> — Second argument: model name (required when first argument is a use case)

swissarmyhammer agent

Manage and interact with Agent Client Protocol (ACP) server.

The agent command provides integration with ACP-compatible code editors, enabling local LLaMA models to be used as coding assistants in editors like Zed and JetBrains IDEs.

Subcommands: acp Start ACP server over stdio for editor integration

Examples: sah agent acp # Start ACP server (stdio) sah agent acp –config config.yaml # Start with custom config

Usage: swissarmyhammer agent [COMMAND]

Subcommands:

• acp — Start ACP server over stdio

swissarmyhammer agent acp

Start Agent Client Protocol (ACP) server for code editor integration.

The ACP server enables SwissArmyHammer to work with ACP-compatible code editors like Zed and JetBrains IDEs. The server communicates over stdin/stdout using JSON-RPC 2.0 protocol.

Features: • Local LLaMA model execution for coding assistance • Session management with conversation history • File system operations (read/write) • Terminal execution • Tool integration via MCP servers • Permission-based security model

Examples: sah agent acp # Start with default config sah agent acp –config acp.yaml # Start with custom config sah agent acp –permission-policy auto-approve-reads sah agent acp –allow-path /home/user/projects –block-path /home/user/.ssh sah agent acp –max-file-size 5242880 –terminal-buffer-size 2097152

Configuration: Options can be specified via:

1. Command-line flags (highest priority)
2. Configuration file (–config)
3. Default values (lowest priority)

Command-line flags override configuration file settings.

For editor configuration: • Zed: Add to agents section in settings • JetBrains: Install ACP plugin and configure

Usage: swissarmyhammer agent acp [OPTIONS]

Options:

• -c, --config <CONFIG> — Path to ACP configuration file (optional)
• --permission-policy <POLICY> — Permission policy: always-ask, auto-approve-reads
• --allow-path <PATH> — Allowed filesystem paths (can be specified multiple times)
• --block-path <PATH> — Blocked filesystem paths (can be specified multiple times)
• --max-file-size <BYTES> — Maximum file size for read operations in bytes
• --terminal-buffer-size <BYTES> — Terminal output buffer size in bytes
• --graceful-shutdown-timeout <SECONDS> — Graceful shutdown timeout in seconds

This document was generated automatically by clap-markdown.

Command-Line Help for avp

This document contains the help content for the avp command-line program.

Installation

brew install swissarmyhammer/tap/avp-cli

Command Overview:

• avp↴
• avp init↴
• avp deinit↴
• avp doctor↴
• avp edit↴
• avp new↴
• avp model↴
• avp model list↴
• avp model show↴
• avp model use↴

avp

AVP - Agent Validator Protocol

Claude Code hook processor that validates tool calls, file changes, and more.

Usage: avp [OPTIONS] [COMMAND]

Subcommands:

• init — Install AVP hooks into Claude Code settings
• deinit — Remove AVP hooks from Claude Code settings and delete .avp directory
• doctor — Diagnose AVP configuration and setup
• edit — Edit an existing RuleSet in $EDITOR
• new — Create a new RuleSet from template
• model — Manage AI model configurations

Options:

• -d, --debug — Enable debug output to stderr

avp init

Install AVP hooks into Claude Code settings

Usage: avp init [TARGET]

Arguments:

• <TARGET> — Where to install the hooks

  Default value: project

  Possible values:

  • project: Project-level settings (.claude/settings.json)
  • local: Local project settings, not committed (.claude/settings.local.json)
  • user: User-level settings (~/.claude/settings.json)

avp deinit

Remove AVP hooks from Claude Code settings and delete .avp directory

Usage: avp deinit [TARGET]

Arguments:

• <TARGET> — Where to remove the hooks from

  Default value: project

  Possible values:

  • project: Project-level settings (.claude/settings.json)
  • local: Local project settings, not committed (.claude/settings.local.json)
  • user: User-level settings (~/.claude/settings.json)

avp doctor

Diagnose AVP configuration and setup

Usage: avp doctor [OPTIONS]

Options:

• -v, --verbose — Show detailed output including fix suggestions

avp edit

Edit an existing RuleSet in $EDITOR

Usage: avp edit [OPTIONS] <NAME>

Arguments:

• <NAME> — RuleSet name (kebab-case)

Options:

• --local [alias: project] — Edit in project (.avp/validators/) [default]
• --global [alias: user] — Edit in user-level directory (~/.avp/validators/)

avp new

Create a new RuleSet from template

Usage: avp new [OPTIONS] <NAME>

Arguments:

• <NAME> — RuleSet name (kebab-case)

Options:

• --local [alias: project] — Create in project (.avp/validators/) [default]
• --global [alias: user] — Create in user-level directory (~/.avp/validators/)

avp model

Manage AI model configurations

Usage: avp model [COMMAND]

Subcommands:

• list — List all available models
• show — Show the current model configuration
• use — Apply a specific model to the project

avp model list

List all available models

Usage: avp model list

avp model show

Show the current model configuration

Usage: avp model show

avp model use

Apply a specific model to the project

Usage: avp model use <NAME>

Arguments:

• <NAME> — Model name to apply

Command-Line Help for mirdan

This document contains the help content for the mirdan command-line program.

Installation

brew install swissarmyhammer/tap/mirdan-cli

Command Overview:

• mirdan↴
• mirdan agents↴
• mirdan new↴
• mirdan new skill↴
• mirdan new validator↴
• mirdan new tool↴
• mirdan new plugin↴
• mirdan install↴
• mirdan uninstall↴
• mirdan list↴
• mirdan search↴
• mirdan info↴
• mirdan login↴
• mirdan logout↴
• mirdan whoami↴
• mirdan publish↴
• mirdan unpublish↴
• mirdan outdated↴
• mirdan update↴
• mirdan sync↴
• mirdan doctor↴
• mirdan start↴

mirdan

Mirdan manages skills, validators, tools, and plugins across all detected AI coding agents.

Skills are deployed to each agent’s skill directory (e.g. .claude/skills/, .cursor/skills/). Validators are deployed to .avp/validators/ (project) or $XDG_DATA_HOME/avp/validators/ (global, defaults to ~/.local/share/avp/validators/). Tools are deployed to .tools/ and registered in agent MCP configs. Plugins are deployed to agent plugin directories (e.g. .claude/plugins/).

Environment variables: MIRDAN_REGISTRY_URL Override the registry URL (useful for local testing) MIRDAN_TOKEN Provide an auth token without logging in MIRDAN_CREDENTIALS_PATH Override the credentials file location MIRDAN_AGENTS_CONFIG Override the agents configuration file

Usage: mirdan [OPTIONS] <COMMAND>

Subcommands:

• agents — Detect and list installed AI coding agents
• new — Create a new package from template
• install — Install a package (type auto-detected from contents)
• uninstall — Remove an installed package
• list — List installed packages
• search — Search the registry for skills and validators
• info — Show detailed information about a package
• login — Authenticate with the registry
• logout — Log out from the registry and revoke token
• whoami — Show current authenticated user
• publish — Publish a package to the registry (type auto-detected)
• unpublish — Remove a published package version from the registry
• outdated — Check for available package updates
• update — Update installed packages to latest versions
• sync — Reconcile .skills/ with agent directories and verify lockfile
• doctor — Diagnose Mirdan setup and configuration
• start — Start the Mirdan tray/accessory app

Options:

• -d, --debug — Enable debug output to stderr
• -y, --yes — Skip confirmation prompts (useful for CI/CD)
• --agent <AGENT_ID> — Limit operations to a single agent (e.g. claude-code, cursor)

mirdan agents

Detect and list installed AI coding agents

Usage: mirdan agents [OPTIONS]

Options:

• --all — Show all known agents, not just detected ones
• --json — Output as JSON

mirdan new

Create a new package from template

Usage: mirdan new <COMMAND>

Subcommands:

• skill — Scaffold a new skill (agentskills.io spec)
• validator — Scaffold a new validator (AVP spec)
• tool — Scaffold a new tool (MCP server definition)
• plugin — Scaffold a new plugin (Claude Code plugin)

mirdan new skill

Scaffold a new skill (agentskills.io spec)

Usage: mirdan new skill [OPTIONS] <NAME>

Arguments:

• <NAME> — Skill name (kebab-case, 1-64 chars)

Options:

• --global — Create in agent global skill directories instead of project-level

mirdan new validator

Scaffold a new validator (AVP spec)

Usage: mirdan new validator [OPTIONS] <NAME>

Arguments:

• <NAME> — Validator name (kebab-case, 1-64 chars)

Options:

• --global — Create in $XDG_DATA_HOME/avp/validators/ instead of .avp/validators/

mirdan new tool

Scaffold a new tool (MCP server definition)

Usage: mirdan new tool [OPTIONS] <NAME>

Arguments:

• <NAME> — Tool name (kebab-case, 1-64 chars)

Options:

• --global — Create in $XDG_DATA_HOME/avp/tools/ instead of current directory

mirdan new plugin

Scaffold a new plugin (Claude Code plugin)

Usage: mirdan new plugin [OPTIONS] <NAME>

Arguments:

• <NAME> — Plugin name (kebab-case, 1-64 chars)

Options:

• --global — Create in global plugin directory

mirdan install

Install a package (type auto-detected from contents)

Usage: mirdan install [OPTIONS] <PACKAGE>

Arguments:

• <PACKAGE> — Package name, name@version, ./local-path, owner/repo, or git URL

Options:

• --global — Install globally
• --git — Treat package as a git URL (clone instead of registry lookup)
• --skill <SKILL> — Install a specific package by name from a multi-package repo
• --mcp — Install as an MCP server instead of a skill/validator
• --command <COMMAND> — MCP server command (binary to run). Required when –mcp is set
• --args <ARGS> — MCP server arguments

mirdan uninstall

Remove an installed package

Usage: mirdan uninstall [OPTIONS] <NAME>

Arguments:

• <NAME> — Package name

Options:

• --global — Remove from global locations

mirdan list

List installed packages

Usage: mirdan list [OPTIONS]

Options:

• --skills — Show only skills
• --validators — Show only validators
• --tools — Show only tools
• --plugins — Show only plugins
• --json — Output as JSON

mirdan search

Search the registry for skills and validators

With a query argument, performs a single search and prints results. Without a query, enters interactive fuzzy search mode.

Usage: mirdan search [OPTIONS] [QUERY]

Arguments:

• <QUERY> — Search query (omit for interactive mode)

Options:

• --json — Output as JSON

mirdan info

Show detailed information about a package

Usage: mirdan info <NAME>

Arguments:

• <NAME> — Package name

mirdan login

Authenticate with the registry

Opens a browser for OAuth login. The registry URL can be overridden with MIRDAN_REGISTRY_URL for local testing.

Usage: mirdan login

mirdan logout

Log out from the registry and revoke token

Usage: mirdan logout

mirdan whoami

Show current authenticated user

Usage: mirdan whoami

mirdan publish

Publish a package to the registry (type auto-detected)

Auto-detects package type from directory contents: - SKILL.md present -> publishes as a skill - VALIDATOR.md + rules/ present -> publishes as a validator - TOOL.md present -> publishes as a tool - .claude-plugin/plugin.json present -> publishes as a plugin

Usage: mirdan publish [OPTIONS] [SOURCE]

Arguments:

• <SOURCE> — Path or git URL to the package directory to publish

  Default value: .

Options:

• --dry-run — Validate and show what would be published without uploading

mirdan unpublish

Remove a published package version from the registry

Usage: mirdan unpublish <NAME_VERSION>

Arguments:

• <NAME_VERSION> — Package name@version (e.g. my-skill@1.0.0)

mirdan outdated

Check for available package updates

Usage: mirdan outdated

mirdan update

Update installed packages to latest versions

Usage: mirdan update [OPTIONS] [NAME]

Arguments:

• <NAME> — Specific package to update (all if omitted)

Options:

• --global — Update global packages

mirdan sync

Reconcile .skills/ with agent directories and verify lockfile

Usage: mirdan sync [OPTIONS]

Options:

• --global — Sync global locations

mirdan doctor

Diagnose Mirdan setup and configuration

Usage: mirdan doctor [OPTIONS]

Options:

• -v, --verbose — Show detailed output including fix suggestions

mirdan start

Start the Mirdan tray/accessory app

Usage: mirdan start