Commit Message Generator

Generate conventional commit messages from git diff changes.

3|Updated Sep 16, 2025

Search Tags:#automation #git #commit #standards #diff #message #conventional-commit

Ready to run

npx skills add https://github.com/mkaczkowski/ai-command-library --skill commit-message-generator-mkaczkowski

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Commit Message Generator
Source: https://github.com/mkaczkowski/ai-command-library/tree/main/plugins/common/skills/commit-helper
Command: npx skills add https://github.com/mkaczkowski/ai-command-library --skill commit-message-generator-mkaczkowski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing clear, consistent commit messages from code changes is time-consuming and error-prone. This Skill guides you to generate concise messages that accurately describe what changed and why, improving history readability and review efficiency.

Core Features & Use Cases

Generate a concise summary from a git diff that highlights what changed.
Enforce conventional-commit style with a structured body and optional footer for issue references.
Streamline code reviews and history navigation by providing consistent, machine-friendly messages.

Quick Start

Provide the staged diff with git diff --staged and ask the AI to generate a concise conventional commit message.

Frequently Asked Questions about Commit Message Generator

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

FAQPage Schema

How do I generate a conventional commit message from a git diff?▼

Generating a conventional commit message from a git diff requires providing the staged changes to the AI, which then formats the what and why into a structured summary, body, and footer.

What is the conventional commit format for writing git commit messages?▼

The conventional commit format structures messages with a concise summary, a body explaining what changed and why, and an optional footer for issue tracker references to ensure machine-friendly history.

Can I auto-link issue trackers when generating commit messages from staged changes?▼

Yes, you can auto-link issue trackers by generating a commit message that includes an optional footer with related issue references, adhering to conventional commit standards for tracker integration.

Do I need to stage my changes before generating a conventional commit message?▼

Yes, you need to stage your changes first. Providing the output of git diff --staged ensures the generated conventional commit message accurately reflects only the ready changes.

Why use conventional commit messages for git history navigation?▼

Using conventional commit messages for git history improves readability and review efficiency by providing consistent, machine-friendly summaries of what changed and why across the project history.

Does the generated commit message follow my project's specific conventions?▼

The generated commit message adheres to conventional commit standards and can be adjusted to match your project's specific conventions, ensuring the summary, body, and footer align with your history guidelines.