commit-message
Write a clear git commit message from the staged changes. Use when the user asks for a commit message, or to summarize what they are about to commit.
Datos de origen
- Repositorio
- codewhale-hq/codewhale-plugin-marketplace
- Última actividad en el origen
- 5 de octubre de 2026 a las 09:24
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 5
- Forks
- 2
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- commit-message
- description
- Write a clear git commit message from the staged changes. Use when the user asks for a commit message, or to summarize what they are about to commit.
# Commit message
1. Read the staged change with `git diff --cached --stat` and then
`git diff --cached`. If nothing is staged, say so and stop; do not stage files.
2. Write the message from what the diff does, not from file names:
- Subject line: imperative mood, 50 characters or fewer if possible, no
trailing period ("Fix retry loop on timeout").
- Blank line, then a body wrapped near 72 columns that explains why the
change is needed and anything a reviewer could miss. Omit the body for a
trivial change.
3. Mention behavior changes, migrations and removed options explicitly.
4. Return the message in a code block. Do not run `git commit` unless the user
asks you to.
Ver en GitHub