Menú
Analyze staged/unstaged changes and create a git commit that follows the project's detected conventions. Use when the user asks to commit, create a commit, or save changes to git. Push only if the user explicitly says "then push" in the same request.
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
Render prose responses in bionic reading style by bolding the leading portion of each word, leaving code, paths, and commands untouched. Use when the user asks for bionic reading / bionic mode / bold-prefix formatting, or to toggle it off ("stop bionic", "normal formatting").
Resolve git merge conflicts by semantically merging both sides of each conflict. Use when the user has merge conflicts, asks to resolve conflicts, or is stuck in a merge/rebase with conflict markers.
Review and freshen all documentation and notes in the current project — discover and obey the project's own doc conventions, fix drift, flag quality gaps, and fill genuinely missing context. Use when the user asks to update docs, freshen documentation, audit AGENTS.md/rules, or clean up notes.
Iteratively review and simplify uncommitted changes until clean or stuck. Use when the user asks to polish, clean up, or iteratively improve uncommitted code changes.
Run the full wrap-up pipeline — polish, then docs-revise, then a single commit — in one deliberate pass. Use ONLY when the user explicitly asks to run polish, docs-revise, and commit together as one pipeline (e.g. "/ship", "polish docs-revise and commit", "wrap this up and ship it"). Do NOT auto-trigger for a plain "clean this up", "commit", "polish", or "update docs" request — those are the individual skills.
Writing voice profile for AI-drafted communication. Provides channel-specific style samples and anti-patterns under profiles/ — pick the file matching the output destination (PR comment, chat, commit message, formal email). Use when the user says "draft in my voice", "rewrite this like I'd say it", or another skill needs a consistent writing register. This skill does not know about its consumers.
| name | commit |
| description | Analyze staged/unstaged changes and create a git commit that follows the project's detected conventions. Use when the user asks to commit, create a commit, or save changes to git. Push only if the user explicitly says "then push" in the same request. |
Create a commit whose message matches how this repo already writes commits. Push only on explicit request.
1. Verify git state
Run git status --short. If this is not a git repo or there are no changes, stop and say so.
2. Learn project conventions
git log --oneline -30
Also read any project docs that state commit rules (README, AGENTS.md, .cursor/rules/).
Determine: format (conventional, ticket-prefixed, plain), casing, scope style, body usage. Match the detected pattern exactly. Never default to conventional commits if the project uses something else.
2b. Load voice profile (if it exists)
Read .cursor/skills/voice/profiles/commit-messages.md and .cursor/skills/voice/profiles/anti-patterns.md. These fill gaps the project pattern does not constrain (verb mood, abbreviations). The project pattern always wins on conflicts. Skip silently if the files do not exist.
3. Stage changes
If nothing is staged, stage modified tracked files with git add -u. Then run git diff --cached --stat.
4. Commit
git commit -m "$(cat <<'EOF'
<message matching project pattern>
EOF
)"
Scan the draft against the voice anti-patterns before committing.
5. Push — only if explicitly requested
Push only if the user said "push" in this same request. Prior approvals do not carry forward.
git log first. Never guess the commit format.