commit-messages

# Commit Messages

Use this skill to generate clear, conventional commit messages that explain the "why" not just the "what". Follow this guide when writing commit messages or helping users structure their commits.

## When to Use

- User asks for help writing a commit message
- User wants to understand conventional commit format
- User needs to split a large commit into smaller ones
- User asks about commit best practices

## Philosophy

- **Why > What** - The diff shows what changed; the message explains why
- **Atomic commits** - One logical change per commit
- **Future readers** - Write for someone debugging at 2am in 6 months
- **Searchable** - Make it easy to find with `git log --grep`

## Format

Follow [Conventional Commits](https://www.conventionalcommits.org/):

```
type(scope): subject

body (optional)

footer (optional)
```

## Types

| Type       | When to Use                                    | Example                               |
| ---------- | ---------------------------------------------- | ------------------------------------- |
| `feat`     | New feature for the user                       | `feat(auth): add password reset flow` |
| `fix`      | Bug fix for the user                           | `fix(cart): correct quantity calc`    |
| `docs`     | Documentation only changes                     | `docs: update API examples`           |
| `style`    | Formatting, white-space (not CSS)              | `style: format with biome`            |
| `refactor` | Code change that neither fixes nor adds        | `refactor: extract validation utils`  |
| `perf`     | Performance improvement                        | `perf: memoize expensive calculation` |
| `test`     | Adding or updating tests                       | `test: add auth integration tests`    |
| `build`    | Build system or dependencies                   | `build: upgrade to node 22`           |
| `ci`       | CI configuration                               | `ci: add playwright to pipeline`