commit-message

Name: commit-message
Availability: InStock
Author: achhina

Generate conventional commit messages from staged git diffs.

Updated Aug 23, 2026

Search Tags:#automation #git #diffs #version-control #commit-message #conventional-commits

Ready to run

npx skills add https://github.com/achhina/dotfiles --skill commit-message-achhina

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/achhina/dotfiles/tree/main/nix/home-manager/modules/coding-agents/claude/skills/commit-message
Command: npx skills add https://github.com/achhina/dotfiles --skill commit-message-achhina

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates clear, conventional commit messages by analyzing staged changes and recent history, ensuring consistency and clarity.

Core Features & Use Cases

Analyze staged changes: run git diff --staged to see what will be committed
Follow conventional format: produce a type, subject, and optional body
Body when needed: include motivation and context for complex changes

Quick Start

Stage your changes and run the commit-message generator to produce a conventional commit message, then paste into your commit command, e.g., git commit -m "<generated message>"

Frequently Asked Questions about commit-message

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

FAQPage Schema

How do I generate conventional commit messages from my staged changes?▼

Conventional commit messages follow a strict format with a type (feat, fix, docs, style, refactor, perf, test, chore, ci, build), subject line limited to 50 characters in lowercase, and optional body wrapped at 72 characters. Stage your changes with git, then run the commit-message generator to analyze the diff and produce a formatted message ready to paste into git commit -m.

What is the conventional commits specification and why does it matter?▼

Conventional commits is a standardized format for git commit messages that enables automated changelog generation, semantic versioning, and clear commit history. It enforces consistent structure—type, subject, and body—making diffs easier to review and version control more traceable across teams.

Can I automate commit message generation from git diffs?▼

Yes. This Skill analyzes staged changes and recent commit history to automatically generate conventional commit messages. It examines your git diff --staged output and produces a formatted message that complies with the strict type taxonomy and formatting rules, eliminating manual formatting.

How should I format commit message subjects and bodies?▼

Commit subjects must be present tense, no more than 50 characters, lowercase after the colon, with no period. Bodies should wrap at 72 characters and provide motivation and context. The conventional-commits specification enforces these constraints to keep history clean and machine-parseable.

What commit types does the conventional commits specification include?▼

The specification defines 10 types: feat (new feature), fix (bug fix), docs (documentation), style (formatting), refactor (code restructuring), perf (performance), test (testing), chore (maintenance), ci (CI/CD), and build (build system). Each type signals the nature of the change in your version control history.