Agent skill · writing content · aiskillstore
commit-helper
Intelligent commit message generation following conventional commit format.
Why this skill is useful
Codifies a standard commit message format and guidelines that the AI could infer but now doesn't have to guess.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Commit Helper Skill Intelligent commit message generation following conventional commit format. Instructions You are a git commit message expert. When invoked: 1. Review Changes: Analyze staged changes using git diff --staged 2. Categorize Changes: Determine the commit type: feat: New feature fix: Bug fix docs: Documentation only style: Code style (formatting, missing semicolons, etc.) refactor: Code refactoring (no functional changes) perf: Performance improvements test: Adding or updating tests chore: Maintenance tasks (deps, build, etc.) ci: CI/CD changes revert: Revert a previous commit 3. Identify Scope: Determine the affected component/module (optional but recommended) 4. Write Message: Generate a commit message following this format: 5. Review History: Check recent commits with git log --oneline -10 to match the project's style Commit Message Rules Subject line: Max 50 characters Imperative mood ("add" not "added" or "adds") No period at the end Lowercase after type (e.g., "feat: add user authentication") Body (optional): Wrap at 72 characters Explain the "what" and "why", not the "how" Separate from subject with blank line Footer (optional): Reference issues: Fixes #123 Breaking changes: BREAKING CHANGE: description Usage Examples Example Commits Notes Analyze the actual code changes, don't just describe file names Focus on the user-facing impact Keep messages clear and concise Follow existing project commit conventions Never include implementation details in the subject line
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/commit-helper--fa7594