<!-- Generated by scripts/generate-site-content.py — do not edit by hand -->


# claude-command-name-format

Command Name section should be 'plugin-name:command-name'

*Formerly known as `command-name-format`. The legacy name still works in configs, `--rule`/`--skip-rule`, suppression comments, and baselines.*

| | |
|---|---|
| **Severity** | warning (disabled) |
| **Autofix** | - |
| **Since** | v0.1.0 |
| **Category** | [Claude Code](claude.md) |

## Why

The Name section in a command file tells users and tools the command's
fully qualified identifier. It must follow the `plugin-name:command-name`
format so the runtime can route invocations correctly.

## Examples

**Bad (in plugin `my-plugin`, file `deploy.md`):**

```markdown
## Name

deploy
```

**Good:**

```markdown
## Name

my-plugin:deploy
```

## How to fix

Update the Name section to include the plugin name prefix followed by
a colon and the command name: `plugin-name:command-name`.

## Configuration

```yaml
rules:
  claude-command-name-format:
    enabled: false  # true | false | auto
    severity: warning
```


*Run `skillsaw explain claude-command-name-format` to see this documentation and the rule's effective configuration in your terminal.*