Agent skill · writing content · aiskillstore
commit-prepare
Prepare git commit messages following conventional commits. Activates on: commit, prepare commit, commit this, commit message, ready to commit, stage and commit
Why this skill is useful
Adds a structured workflow for generating conventional commit messages, which the AI wouldn't reliably create on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Commit Preparation Skill Automatically prepare commit messages following conventional commits standard. Activation This skill activates on keywords: "commit", "prepare commit", "commit this" "commit message", "write commit" "stage and commit", "commit changes" "what should I commit", "ready to commit" Workflow When activated, follow these steps: 1. Gather Context Run these commands to understand what's being committed: 2. Analyze Changes Determine: Type: feat, fix, docs, refactor, test, chore, perf, ci Scope: Which component/module is affected (optional) Breaking: Are there breaking changes? What: What was changed Why: Why was it changed (if not obvious) 3. Generate Commit Message Follow conventional commits format: Type Reference Type When to Use Example ------ ------------- --------- feat New feature feat: add user authentication fix Bug fix fix: resolve null pointer in parser docs Documentation only docs: update API reference refactor Code restructuring refactor: extract validation logic test Adding/fixing tests test: add unit tests for auth perf Performance improvement perf: optimize database queries chore Maintenance, deps chore: update dependencies ci CI/CD changes ci: add caching to workflow style Formatting only style: fix indentation Rules Subject: Imperative mood ("add" not "added"), no period, max 50 chars Body: Wrap at 72 chars, explain what and why (not how) Footer: Breaking changes, issue references 4. Handle Staging If there are unstaged changes, ask: "Stage all changes?" (git add .) "Stage specific files?" (list them) "Review changes first?" (show diff) 5. Execute Commit After user confirms the message: Important: Always use HEREDOC for multi-line commits: 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/commit-prepare