commit-message-helper

RiANOl's avatarfrom RiANOl

Helps write Git commit messages following the Conventional Commits specification. Use this skill when the user asks to commit changes, write commit messages, or mentions git commits.

⭐3stars🔀0forks📁View on GitHub🕐Updated Jan 5, 2026

When & Why to Use This Skill

The Commit Message Helper is a specialized Claude skill designed to streamline version control workflows by generating Git commit messages that strictly adhere to the Conventional Commits specification. It ensures consistency, readability, and machine-parseability across project histories, making it an essential tool for professional software development teams and individual developers aiming for high-quality documentation.

Use Cases

  • Standardizing Project History: Automatically generate structured commit messages (e.g., feat, fix, docs) to maintain a clean, professional, and searchable repository log.
  • Automated Changelog Generation: Facilitate the use of automated tools that parse structured commit messages to generate release notes and manage semantic versioning.
  • Team Collaboration and Compliance: Enforce team-wide adherence to standardized commit conventions without requiring manual memorization of formatting rules.
  • Workflow Efficiency: Quickly draft descriptive and compliant commit messages directly within the development context, reducing the cognitive load of context-switching.
  • Educational Guidance: Assist junior developers in learning and applying industry-standard Git best practices through real-time examples and validation.
namecommit-message-helper
descriptionHelps write Git commit messages following the Conventional Commits specification. Use this skill when the user asks to commit changes, write commit messages, or mentions git commits.

Commit Message Helper

When writing commit messages, follow these rules:

Format

():

Types

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • chore: Changes to the build process or auxiliary tools

Guidelines

  1. Subject line should be no longer than 50 characters
  2. Use imperative mood ("add feature" not "added feature")
  3. Do not end the subject line with a period
  4. Separate subject from body with a blank line
  5. Use the body to explain what and why, not how

Examples

Good: feat(auth): add OAuth2 login support

Implement OAuth2 authentication flow to allow users to log in with their Google or GitHub accounts.

Closes #123

Bad: updated stuff

Validation

Before committing, run the validation script to check the format:

python scripts/validate_commit.py "your commit message"