Git Commit
- 41 installs
- 251 repo stars
- Updated August 4, 2026
- fredrikaverpil/dotfiles
Ensures git commit messages follow the Conventional Commits specification and prompts for a Jira ticket number.
About
Defines the Conventional Commits format with type, scope, description, and footers to apply before running git commit. A developer uses it to keep commit messages consistent and reference the related Jira ticket.
- Conventional Commits format with a table of types
- Prompts for a Jira ticket number before committing
Git Commit by the numbers
- 41 all-time installs (skills.sh)
- Ranked #320 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/fredrikaverpil/dotfiles --skill git-commitAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 41 |
|---|---|
| repo stars | ★ 251 |
| Last updated | August 4, 2026 |
| Repository | fredrikaverpil/dotfiles ↗ |
What it does
Ensures git commit messages follow the Conventional Commits specification and prompts for a Jira ticket number.
Files
Git Commit Messages
Write commit messages following the Conventional Commits specification.
Format
<type>(<scope>): <description>
[optional body]
[optional footer(s)]Types
| Type | Purpose |
|---|---|
feat | New feature |
fix | Bug fix |
docs | Documentation only |
style | Code style (formatting, no logic change) |
refactor | Code change that neither fixes a bug nor adds a feature |
perf | Performance improvement |
test | Adding or correcting tests |
build | Build system or external dependencies |
ci | CI configuration |
chore | Maintenance tasks |
revert | Reverts a previous commit |
Rules
1. Use imperative mood in description ("add feature" not "added feature") 2. Do not end description with a period 3. Keep description under 72 characters 4. Separate subject from body with a blank line 5. Use the body to explain intent, nuances, gotchas, or background behind the change — not a paraphrase of the diff 6. Always ask the user for the Jira ticket number before committing. If there is one, include it as the last line in the commit body (e.g., XY-123). If there isn't one, omit it.
Breaking Changes
Add ! after type/scope or include BREAKING CHANGE: in footer:
feat(api)!: remove deprecated endpoints
BREAKING CHANGE: The /v1/users endpoint has been removed.Scope
Optional. Use to specify area of change (e.g., api, ui, auth, db).
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148