Agent skill · software engineering · aiskillstore
git-commit-helper
Generate descriptive commit messages by analyzing git diffs. Use when
Why this skill is useful
Codifies a specific commit message format and guidelines that the AI could infer but now doesn't have to guess.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Git Commit Helper Quick start Analyze staged changes and generate commit message: Commit message format Follow conventional commits format: Types feat: New feature fix: Bug fix docs: Documentation changes style: Code style changes (formatting, missing semicolons) refactor: Code refactoring test: Adding or updating tests chore: Maintenance tasks Examples Feature commit: Bug fix: Refactor: Analyzing changes Review what's being committed: Commit message guidelines DO: Use imperative mood ("add feature" not "added feature") Keep first line under 50 characters Capitalize first letter No period at end of summary Explain WHY not just WHAT in body DON'T: Use vague messages like "update" or "fix stuff" Include technical implementation details in summary Write paragraphs in summary line Use past tense Multi-file commits When committing multiple related changes: Scope examples Frontend: feat(ui): add loading spinner to dashboard fix(form): validate email format Backend: feat(api): add user profile endpoint fix(db): resolve connection pool leak Infrastructure: chore(ci): update Node version to 20 feat(docker): add multi-stage build Breaking changes Indicate breaking changes clearly: Template workflow 1. Review changes: git diff --staged 2. Identify type: Is it feat, fix, refactor, etc.? 3. Determine scope: What part of the codebase? 4. Write summary: Brief, imperative description 5. Add body: Explain why and what impact 6. Note breaking changes: If applicable Interactive commit helper Use git add -p for selective staging: Amending commits Fix the last commit message: Reference Files references/GITCOMMIT.template.md - Conventional commits format template with types, scopes, and examples Best practices 1. Atomic commits - One logical change per commit 2. Test before commit - Ensure code works 3. Reference issues - Include issue numbers if applicable 4. Keep it focused - Don't mix unrelated changes 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/git-commit-helper