commit-message-generator

Generate conventional commit messages from staged git changes.

16|4|Updated Oct 13, 2025
One-click install
npx skills add https://github.com/kanopi/cms-cultivator --skill commit-message-generator-kanopi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-message-generator
Source: https://github.com/kanopi/cms-cultivator/tree/main/skills/commit-message-generator
Command: npx skills add https://github.com/kanopi/cms-cultivator --skill commit-message-generator-kanopi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automatically generates conventional commit messages for staged changes, helping teams maintain a clean, understandable project history and improves automation for changelogs and releases.

Core Features & Use Cases

  • Analyze git status and diff to craft precise conventional messages.
  • Suggest type, scope, and description aligned with project conventions.
  • Support multi-change scenarios and generate either multiple commits or a single, well-scoped message.
  • Use case: when preparing to commit changes and you want consistent messaging across a workflow.

Quick Start

Describe your staged changes and I will generate a conventional commit message for review.

Frequently Asked Questions about commit-message-generator

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

FAQPage Schema
How do I automatically generate conventional commit messages for staged git changes?

Conventional commit messages are automatically generated by analyzing your git diff, previous commit style, and scope suggestions to ensure consistent, meaningful messaging across your project history.

Can I generate a single commit message for multiple staged changes?

Yes, multiple staged changes are supported by generating either multiple granular commits or a single, well-scoped conventional commit message based on the analyzed git diff.

Does this tool follow the standard conventional commits format with types and scopes?

Yes, it suggests the commit type, scope, and description aligned with your project conventions, handling common scenarios such as features, fixes, and refactors.

How do conventional commit messages improve git workflow and release automation?

Conventional commit messages improve git workflow by maintaining a clean, understandable project history, which directly enables and improves automation for changelogs and releases.

What is the best way to ensure my commit messages match my project's existing style?

To match your existing style, the generator analyzes previous commit conventions alongside your staged changes and user-provided scope suggestions to craft aligned messages.

Do I need to manually write the commit type and scope for a refactor?

No, for refactors and other common scenarios like features or fixes, the tool automatically suggests the appropriate type and scope based on the analyzed git status and diff.