skills.rest
grumps
grumpsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Commit Message Standards

Generate conventional commit messages from staged Git changes.

Updated Nov 17, 2025
Search Tags:#code quality#git#workflow#developer tools#version control#conventional commits#commit messages
One-click install
npx skills add https://github.com/grumps/claude-dotfiles --skill commit-message-standards
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Commit Message Standards
Source: https://github.com/grumps/claude-dotfiles/tree/main/skills/commits
Command: npx skills add https://github.com/grumps/claude-dotfiles --skill commit-message-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent or poorly written commit messages hinder code review, debugging, and project history analysis. This skill ensures all your Git commits adhere to the Conventional Commits standard, making your project history clean, readable, and easy to navigate.

Core Features & Use Cases

  • Conventional Commit Generation: Automatically generate commit messages following the <type>(<scope>): <subject> format, including body and footer sections.
  • Contextual Analysis: Analyzes your staged changes (git diff --cached) to suggest the most appropriate commit type, scope, and subject.
  • Git Hook Integration: Can be integrated with the prepare-commit-msg Git hook to auto-generate messages before you even type.
  • Use Case: After making changes, simply ask Claude to /commit. The skill will analyze your modifications and propose a perfectly formatted commit message, saving you time and ensuring consistency across your team's contributions.

Quick Start

Ask Claude to "Generate a conventional commit message for my staged changes."

Frequently Asked Questions about Commit Message Standards

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

FAQPage Schema
How do I write better Git commit messages?▼

Conventional Commits is a standard format for Git commit messages using `<type>(<scope>): <subject>` syntax. This structure makes your project history readable, supports automated tooling, and helps teams maintain consistency. The format includes a 50-character subject line, optional body with 72-character wrapping, and footer sections for issue references and breaking changes.

What is the Conventional Commits standard?▼

Conventional Commits is a specification for writing Git messages with structured metadata. Messages follow the pattern: type (feat, fix, docs, style, refactor, etc.), optional scope, and imperative-mood subject. This enables automated changelog generation, semantic versioning, and clearer project history navigation across teams.

Can I automate commit message generation in Git?▼

Yes, commit message generation can be integrated with Git's `prepare-commit-msg` hook to automatically suggest formatted messages before you write them. The hook analyzes your staged changes with `git diff --cached` to propose the appropriate type, scope, and subject, ensuring consistency without manual formatting work.

How do I use conventional commits with version control workflows?▼

After staging changes with Git, request a commit message analysis to generate a Conventional Commits-formatted message. The tool examines your diff to determine commit type and scope, then produces a formatted message with proper subject length, body wrapping, and footer structure for your team's code review and project history.

What are the rules for commit message formatting?▼

Conventional Commits enforce: type prefix (feat, fix, docs, style, refactor, chore, test), optional scope in parentheses, imperative-mood subject capped at 50 characters, blank line before body, body text wrapped at 72 characters, and optional footer for breaking-change notices and issue references.

Does this work with my existing Git workflow?▼

Yes. This integrates with standard Git workflows via the `prepare-commit-msg` hook or on-demand requests. It analyzes staged changes and generates messages matching your team's Conventional Commits adoption, supporting features, fixes, documentation updates, style changes, refactors, and other codebase modifications without altering your Git commands.

Related Skills

Explore More Software Engineering Skills→
RoentekRoentek
4

auto-stage-commit

Stage the git working tree and generate a Conventional Commits message.

Official
Intermediate
mrp4stenmrp4sten
3

conventional-commits

Generate structured Git commit messages with conventional types and scopes.

Community
Advanced
GaryOcean428GaryOcean428

git-workflow

Enforce conventional commits, branch naming, Gitflow, and PR hygiene.

Community
Advanced
beyondwenbeyondwen

chinese-commit-conventions

Apply Chinese-adapted Conventional Commits rules to standardize commit messages.

Community
Advanced