git-commit-guidelines

This skill should be used when the user asks to "write a commit message", "format commit", "commit message style", or needs guidance on conventional commit format.

⭐4stars🔀0forks📁View on GitHub🕐Updated Jan 9, 2026

When & Why to Use This Skill

This Claude skill streamlines the software development workflow by providing expert guidance on writing standardized, professional Git commit messages. It helps developers adhere to the Conventional Commits specification, ensuring project histories are readable, searchable, and compatible with automated changelog generation and semantic versioning tools.

Use Cases

  • Standardizing repository history: Helping engineering teams maintain a consistent commit style across large-scale or open-source projects.
  • Automating release notes: Ensuring commit messages follow the 'feat' and 'fix' patterns required for automated tools like semantic-release to generate accurate changelogs.
  • Enhancing code review efficiency: Assisting developers in drafting clear, imperative-style summaries that provide immediate context to reviewers regarding the intent of code changes.
  • Onboarding junior developers: Serving as a real-time reference for team-specific or industry-standard commit conventions and best practices.
nameGit Commit Guidelines
descriptionThis skill should be used when the user asks to "write a commit message", "format commit", "commit message style", or needs guidance on conventional commit format.

Git Commit Guidelines

This skill provides guidance for writing conventional commit messages.

Commit Message Format

<type>(<scope>): <subject>

<body>

<footer>

Types

Type Description
feat New feature
fix Bug fix
docs Documentation only
style Formatting, no code change
refactor Code change, no feature/fix
test Adding tests
chore Maintenance tasks

Rules

  1. Subject line max 50 characters
  2. Use imperative mood ("Add feature" not "Added feature")
  3. No period at end of subject
  4. Blank line between subject and body
  5. Body explains what and why, not how

Examples

Good:

feat(auth): add OAuth2 login support

Implement Google and GitHub OAuth providers.
Closes #123

Bad:

Updated the login page to support OAuth

Quick Reference

  • feat: New functionality for users
  • fix: Bug fix for users
  • docs: Documentation changes
  • refactor: Code restructuring
  • test: Test additions/changes
  • chore: Build, CI, dependencies