Jacopalas /palas-git:commit — Create Consistent Git Commits
IMPORTANT: Before starting execution, inform the user: "ESTOY EJECUTANDO EL SKILL /palas-git:commit"
Create git commits with well-structured, conventional commit messages. All commit messages MUST be written in Spanish.
Usage
/git:commit [message]
Arguments:
message(Optional): Commit message or description of changes. If omitted, analyze staged changes automatically.
Commit Message Format
Follow Conventional Commits format:
<type>(<scope>): <subject>
<body>
Types
| Type | Description |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation only |
style |
Formatting, no code change |
refactor |
Code restructuring, no behavior change |
perf |
Performance improvement |
test |
Adding or fixing tests |
chore |
Build, config, dependencies |
ci |
CI/CD changes |
Scope
Optional. Component or area affected (e.g., auth, api, ui).
Subject
- Imperative mood ("añade función" not "añadida función")
- No period at end
- Max 50 characters
- Always in Spanish
Body
- Explain why, not what (code shows what)
- Wrap at 72 characters
- Optional for small changes
- Always in Spanish
Behavior
- Check git status: Run
git statusto see changes - Check staged files: Run
git diff --staged --stat - Check recent commits: Run
git log --oneline -5for style reference - Analyze changes: Determine type and scope from files changed
- Draft message: Create commit message following format
- Stage if needed: Add relevant files if not staged
- Commit: Execute
git commitwith message - Verify: Run
git statusto confirm
Examples
/git:commit
-> Analyzes staged changes, drafts appropriate message in Spanish
/git:commit add user authentication
-> Creates: feat(auth): añade autenticación de usuario
/git:commit fix login redirect bug
-> Creates: fix(auth): corrige bug de redirección en login
/git:commit update README with installation steps
-> Creates: docs: actualiza README con pasos de instalación
Commands
# Check current state
git status
git diff --staged --stat
git log --oneline -5
# Stage specific files (prefer over git add -A)
git add path/to/file1.ts path/to/file2.ts
# Commit with HEREDOC for proper formatting (message in Spanish)
git commit -m "$(cat <<'EOF'
type(scope): línea de asunto en español
Cuerpo explicando por qué se hizo este cambio.
EOF
)"
# Verify
git status
Rules
- Always write commit messages in Spanish — subject and body must be in Spanish
- Never use
git add -A— stage specific files to avoid accidents - Never commit secrets — skip
.env, credentials, API keys - Never amend without asking — amending can lose work
- Never push automatically — commit only, user pushes manually
- Never skip hooks — let pre-commit hooks run
Multi-File Commits
When changes span multiple files:
- Group related changes into one commit
- Use scope to indicate main area
- List affected areas in body if helpful
feat(api): añade limitación de tasa
- Añade middleware de rate limit
- Actualiza rutas de API
- Añade tests de rate limit
Notes
- If pre-commit hooks fail, fix issues and create a NEW commit (don't amend)
- For large changes, consider splitting into smaller commits
- Always verify with
git statusafter committing