Agent skill · software engineering · aiskillstore
commit
Generate commit messages following project conventions for staged changes. Use when the user asks to commit changes or run /commit.
Why this skill is useful
Codifies a specific commit message format and conventions that the AI could infer but now doesn't have to guess.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Commit Message Generator Generate commit messages following project conventions for staged changes. Instructions When this skill is invoked: 1. Run git diff --staged to review the staged changes 2. Run git status to understand the overall state 3. Run git log --oneline -10 to see recent commit style for context 4. Analyze what was changed and why 5. Generate a commit message following the format below 6. Present the commit message to the user for approval - keep it concise, just show the message and ask for approval 7. If approved, execute the commit Presentation Style: Be direct and minimal. Present only the commit message and ask "Proceed with this commit message?" - no analysis, explanations, or bullet points unless the changes are complex or ambiguous. Commit Message Format Types feat - New feature fix - Bug fix refactor - Code restructuring without behavior change test - Adding or updating tests docs - Documentation changes style - Formatting, whitespace (no code change) chore - Build, config, dependency updates Rules 1. First line: Must be under 72 characters 2. Tense: Present tense, imperative mood ("add" not "added" or "adds") 3. Description: Complete the sentence "This commit will..." 4. Body: Optional, use for explaining "why" not "what" 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/commit--aa87ca