Clean commit

Writes the commit message from the actual diff, telling the why and not repeating what the code already says.

Cuándo se usa

Every time you are about to commit.

SKILL.md

# Clean commit

Read the full diff before writing. A message written from memory describes the
intention, not the change.

## The message

- **First line**: up to 72 characters, imperative and present tense. It says what
  the commit does, not what you did.
- **Blank line**, then the why: what problem it solves, what was ruled out and
  why. The what is already in the diff; the why lives only in your head.
- **No filler**: never "various changes" or "minor fixes".
- **The repository's language.** Check git log before deciding.

## Before committing

- One commit, one idea. If the message needs an "and", it is probably two.
- Make sure no local config, keys or leftover debugging slipped in.
- Follow the style the history already has: if it uses prefixes like feat or fix,
  use them; if it does not, do not introduce them.

Never commit unasked, and never push without explicit permission.