Menú
Guided git commit workflow — review changes, draft message, stage, commit
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Manage context pressure during large codebase work without losing critical state.
Create a pull request with structured summary and test plan
Interactive debugging — reproduce, isolate, trace, fix
Explore a codebase or directory to understand its structure and purpose
Implement a requested code change end-to-end with scoped edits and verification.
Investigate production-like failures from symptoms, logs, and reproduction steps.
| name | commit |
| description | Guided git commit workflow — review changes, draft message, stage, commit |
| when_to_use | When the collaborator asks to commit changes or when work reaches a natural commit point |
| required_tools | ["bash"] |
| tags | ["git","workflow"] |
| activation | {"input_patterns":["(?i)(commit|提交)"]} |
${ARGS}
Run git status --short to see all changes. Run git diff to understand what changed and why. Read recent git log --oneline -5 entries to match the repository's commit message conventions.
Classify the change: new feature, enhancement, bug fix, refactor, test, docs, or chore. Identify which files belong together in a single logical commit. Flag anything that should NOT be committed — credentials, build artifacts, unrelated modifications.
Write a concise commit message. First line: imperative verb, what changed, why — under 72 characters. Body only when the diff cannot convey the context alone. Follow the repository's existing convention (conventional commits, etc.).
Stage only the relevant files by name. Avoid git add -A unless every change belongs in one commit. Create the commit. Show the result.
If pre-commit hooks fail: fix the issue, re-stage, create a NEW commit. Never amend without explicit request — amending after hook failure modifies the previous commit, not the failed one.
