create-command

Create Command

Creates new slash commands through a structured workflow: iron-law → brainstorm → design → scaffold → validate. Uses Socratic questioning to refine rough ideas into well-designed commands before generating any files.

When To Use

Use this command when you need to:

• Creating a new slash command from scratch
• Need guided brainstorming for command design
• Want structured workflow for command development

When NOT To Use

Avoid this command if:

• Creating skills - use /create-skill instead
• Creating hooks - use /create-hook instead
• Modifying existing commands - edit directly

Usage

# Start with brainstorming (recommended)
/create-command "run all tests and show coverage report"

# Skip brainstorming if design is clear
/create-command test-coverage --skip-brainstorm

# Create in specific plugin
/create-command "analyze git history" --plugin sanctum

What is a Slash Command?

Slash commands are shortcuts that expand into prompts Claude follows. They're stored as .md files in commands/ and referenced in plugin.json.

Simple command example:

---
description: Run tests with coverage
---

Run all tests with pytest and display a coverage report. Focus on files changed in the current branch.

Command with arguments:

---
description: Review specific PR
usage: /review-pr <pr-number> [--focus security|performance|all]
---

Review pull request #$ARGUMENTS using the code review skill. Focus on ${focus:-all} aspects.

Workflow

Phase 0: Iron Law Interlock (Blocking)

This phase is required and cannot be skipped.

Before any file creation, satisfy the Iron Law interlock:

Step 1: Create Test File FIRST

# Determine test location based on target plugin
tests/unit/test_${command_name}_command.py

Step 2: Write Structural Validation Tests

"""Tests for ${command_name} command structure and validation.

Written BEFORE implementation per Iron Law.
"""
import json
from pathlib import Path
import pytest

class Test${CommandName}Command:
    """Test /${command_name} command structure."""

    @pytest.fixture
    def command_file_path(self) -> Path:
        return Path(__file__).parents[2] / "commands" / "${command_name}.md"

    @pytest.fixture
    def plugin_json_path(self) -> Path:
        return Path(__file__).parents[2] / ".claude-plugin" / "plugin.json"

    def test_should_exist_when_command_file_path_resolved(
        self, command_file_path: Path
    ) -> None:
        """Command file must exist."""
        assert command_file_path.exists()

    def test_should_have_frontmatter_when_parsing_content(
        self, command_file_path: Path
    ) -> None:
        """Command must have valid frontmatter."""
        content = command_file_path.read_text()
        assert content.startswith("---")
        assert "description:" in content

    def test_should_be_registered_in_plugin_json(
        self, plugin_json_path: Path
    ) -> None:
        """Command must be registered in plugin.json."""
        plugin = json.loads(plugin_json_path.read_text())
        commands = plugin.get("commands", [])
        assert any("${command_name}.md" in cmd for cmd in commands)