# Commit > Create well-structured git commits with consistent message format. Use when the user wants to commit changes, make a commit, guardar cambios, hacer commit, or save work to git. - Skill: `jacopalas/commit` (Agent Skill) - Install (CLI): `npx skillmds@latest add jacopalas/commit` - Raw SKILL.md: https://api.skillmd.com/api/skills/jacopalas/commit/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: Jacopalas (https://skillmd.com/u/jacopalas) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/jacopalas/commit --- # /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 ```text /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: ```text (): ``` ### 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 1. **Check git status**: Run `git status` to see changes 2. **Check staged files**: Run `git diff --staged --stat` 3. **Check recent commits**: Run `git log --oneline -5` for style reference 4. **Analyze changes**: Determine type and scope from files changed 5. **Draft message**: Create commit message following format 6. **Stage if needed**: Add relevant files if not staged 7. **Commit**: Execute `git commit` with message 8. **Verify**: Run `git status` to confirm ## Examples ```text /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 ```bash # 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 1. **Always write commit messages in Spanish** — subject and body must be in Spanish 2. **Never use `git add -A`** — stage specific files to avoid accidents 3. **Never commit secrets** — skip `.env`, credentials, API keys 4. **Never amend without asking** — amending can lose work 5. **Never push automatically** — commit only, user pushes manually 6. **Never skip hooks** — let pre-commit hooks run ## Multi-File Commits When changes span multiple files: 1. Group related changes into one commit 2. Use scope to indicate main area 3. List affected areas in body if helpful ```text 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 status` after committing