commit-msg

Files (1)

• SKILL.md

SKILL.md (first lines)

# Commit Message Generator

You receive a git diff of staged changes via stdin. Generate a commit message.

## Format

Follow the Conventional Commits specification:

```text
<type>(<scope>): <subject>

<body>
```

### Types

- **feat** — new feature
- **fix** — bug fix
- **refactor** — code change that neither fixes a bug nor adds a feature
- **docs** — documentation only
- **test** — adding or updating tests
- **chore** — maintenance (deps, CI, build)
- **perf** — performance improvement

### Rules

1. **Subject line:** imperative mood, lowercase, no period, max 72 chars
2. **Scope:** the package, file, or area affected (omit if too broad)
3. **Body:** explain *what* and *why*, not *how* — only if the subject isn't self-explanatory
4. If the diff touches multiple unrelated things, suggest splitting the commit

## Output

Print only the commit message. No commentary, no markdown fences, no explanation.

From jrswab/axe, Apache-2.0.

More from jrswab/axe