commit-changes
Create a well-formatted commit following project conventions. Auto-detects commit style from git history.
Datos de origen
- Repositorio
- anilcancakir/claude-code-plugins
- Última actividad en el origen
- 26 de enero de 2026 a las 13:27
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 6
- Forks
- 1
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-changes
- description
- Create a well-formatted commit following project conventions. Auto-detects commit style from git history.
# Commit Task
Create a commit for staged/unstaged changes following project conventions.
## Steps
1. Check `git status` for changes
2. Analyze `git log --oneline -10` to detect commit style
3. Categorize changes (feat/fix/docs/refactor/test/chore)
4. Generate commit message matching detected style
5. Present to user for approval
6. Execute commit
## Commit Style Detection
Use the detection script for accurate results:
```bash
# Returns JSON with style and confidence
"${CLAUDE_PLUGIN_ROOT}/scripts/detect-commit-style.sh"
```
**Output example:**
```json
{
"style": "conventional-scoped",
"confidence": 80,
"stats": { "total": 10, "conventional_scoped": 8, "gitmoji": 2 }
}
```
| Pattern | Style |
|---------|-------|
| `type(scope): message` | Conventional Commits (scoped) |
| `type: message` | Conventional (no scope) |
| `:emoji: message` | Gitmoji |
| Plain text | Simple |
## Conventional Commits Types
| Type | Use For |
|------|---------|
| feat | New features |
| fix | Bug fixes |
| docs | Documentation only |
| style | Formatting changes |
| refactor | Code restructuring |
| perf | Performance improvements |
| test | Adding/fixing tests |
| chore | Maintenance tasks |
## Message Format
```
<type>(<scope>): <subject>
<body>
<footer>
```
**Subject Rules:**
- Imperative mood ("add" not "added")
- No period at end
- Max 50 characters
- Lowercase
**Body** (optional):
- Explain what and why
- Wrap at 72 characters
**Footer** (optional):
- `Closes #123`
- `BREAKING CHANGE: description`
## Output
Present message for approval before committing.
Ver en GitHub