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


# claude-command-sections

Command files should have Name, Synopsis, Description, and Implementation sections

*Formerly known as `command-sections`. 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

Command files follow a structured format with four recommended
sections: Name, Synopsis, Description, and Implementation. Missing
sections make the command harder for both humans and agents to
understand — the format exists so that each piece of information
has a predictable location.

## Examples

**Bad:**

```markdown
---
description: Deploy to staging
---

Run `make deploy-staging` to deploy.
```

**Good:**

```markdown
---
description: Deploy to staging
---

## Name

my-plugin:deploy-staging

## Synopsis

Deploy the application to the staging environment.

## Description

Runs the staging deployment pipeline...

## Implementation

Run `make deploy-staging`.
```

## How to fix

Add the missing section heading(s) listed in the violation message.
Each section is a `##` heading with the exact name shown.

## Configuration

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


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