commit-messages

Name: commit-messages
Availability: InStock
Author: TheDecipherist

Generate conventional commit messages from git diffs using the Conventional Commits format.

543|45|Updated Jan 14, 2026

Search Tags:#automation #git #versioning #commit #diff #code-review #conventional-commits

Ready to run

npx skills add https://github.com/TheDecipherist/claude-code-mastery --skill commit-messages-thedecipherist

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-messages
Source: https://github.com/TheDecipherist/claude-code-mastery/tree/main/skills/commit-messages
Command: npx skills add https://github.com/TheDecipherist/claude-code-mastery --skill commit-messages-thedecipherist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate clear, conventional commit messages from git diffs to standardize project history.

Core Features & Use Cases

Generate standard commit messages from staged changes using the Conventional Commits spec.
Infer type (feat, fix, docs, etc.), scope, and a concise subject; supports optional body and footer.
Use during staging, code review, and release preparation to maintain a clean, navigable history.

Quick Start

Stage changes and ask the skill to produce a conventional commit message for the current diff.

Frequently Asked Questions about commit-messages

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

FAQPage Schema

How do I generate conventional commit messages from git diffs automatically?▼

Generate conventional commit messages from git diffs by staging changes and asking the skill to analyze the current diff. It infers the type, scope, and subject to standardize your project history.

What is the conventional commits format for staging code review changes?▼

The conventional commits format requires a type, an optional scope, a concise subject, and optional body or footer content. This structure maintains a clean, navigable history during code reviews and releases.

Can I infer the correct commit type and scope from staged git changes?▼

Yes, you can infer the correct commit type and scope from staged git changes. The skill analyzes the diff across modified files to automatically determine the appropriate type like feat or fix.

Does this conventional commits generator work without external dependencies?▼

Yes, the conventional commits generator works without external dependencies. It processes your staged git diff directly to output the required type, scope, and subject formatting.

What's the best way to standardize project history with conventional commits?▼

The best way to standardize project history is to apply the conventional commits spec to every staged diff. This transforms modified files into a consistent format for navigable release preparation.

When should I not use automated conventional commit messages?▼

You should not use automated conventional commit messages when your staged changes span unrelated features requiring distinct commits, as the generator produces a single message for the entire current diff.