skills.rest
fredrikaverpil
fredrikaverpilCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-commit

Validate git commit messages against the Conventional Commits specification.

253|7|Updated Apr 8, 2016
Search Tags:#git#commit#lint#conventional-commits#message
One-click install
npx skills add https://github.com/fredrikaverpil/dotfiles --skill git-commit-fredrikaverpil
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/fredrikaverpil/dotfiles/tree/main/stow/shared/.claude/skills/git-commit
Command: npx skills add https://github.com/fredrikaverpil/dotfiles --skill git-commit-fredrikaverpil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces commit messages follow the Conventional Commits specification, reducing ambiguity and improving release notes and changelogs.

Core Features & Use Cases

  • Enforce format: Validate commit messages against the Conventional Commits specification.
  • Guidance: Provide templates and examples for common change types (feat, fix, docs, etc.).
  • Use Case: Before committing, Claude checks the message and suggests corrections to ensure consistency across the project.

Quick Start

Example: create a commit with a conventional message, e.g. feat(auth): add login flow

Frequently Asked Questions about git-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce conventional commits in my git workflow?▼

Conventional Commits enforce a standardized format for commit messages: type(scope): description. This Skill validates messages against the Conventional Commits specification before commits are created, ensuring consistency across your project and improving automated release notes and changelogs.

What's the correct format for a conventional commit message?▼

Conventional commit messages follow the pattern type(scope): description, where the subject stays under 72 characters in imperative mood without a trailing period. A blank line separates the subject from the body, and optional BREAKING CHANGE footers document breaking changes.

Can I use conventional commits in CI workflows?▼

Yes. This Skill applies commit message validation both in local development before git commit and in CI pipelines, catching format violations early and maintaining message consistency across all contributors and environments.

What commit types does conventional commits support?▼

Conventional Commits define standard change types including feat (features), fix (bug fixes), docs (documentation), and others. This Skill provides templates and guidance for these common types to help developers write consistent, categorized commit messages.

How do I fix a commit message that doesn't follow the convention?▼

This Skill suggests corrections to non-compliant messages before committing, guiding you to reformat subjects, add proper scope notation, correct imperative mood, and structure body and footer sections according to the specification.

Related Skills

Explore More Software Engineering Skills→
jupesjupes
2

setup-pre-commit

Configure Husky pre-commit hooks with lint-staged and Prettier.

Community
Intermediate
daniel-heydari-devdaniel-heydari-dev

changelog-generation

Generate changelogs and enforce semantic versioning from conventional commits.

Community
Intermediate
sunLeeesunLeee

convention-commit

Enforce Conventional Commits format for Git commit messages.

Community
Intermediate
hw-native-syshw-native-sys
101

git-commit

Automate Git commits with pre-commit hooks, testing, and linting.

Official
Advanced