Conventional Commit Generator

Convert git diffs into Conventional Commits messages with optional bodies and footers.

5|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/HirogaKatageri/hirokata-cc-marketplace --skill conventional-commit-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Conventional Commit Generator
Source: https://github.com/HirogaKatageri/hirokata-cc-marketplace/tree/main/plugins/cc-develop-plugin/skills/conventional-commit
Command: npx skills add https://github.com/HirogaKatageri/hirokata-cc-marketplace --skill conventional-commit-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Conventional Commit Generator helps teams automatically convert scattered code changes into standardized conventional commit messages, enabling cleaner changelogs, easier code reviews, and deterministic versioning.

Core Features & Use Cases

  • Analyze staged and unstaged changes, detect modified files, and group them by logical feature and scope.
  • Generate multiple commits following the Conventional Commits specification, with optional bodies and breaking-change footers.
  • Support interactive commit grouping decisions and produce ready-to-run git commands for seamless integration in workflows.

Quick Start

Run the tool to generate commits for your current repository state:

  • Scan your git working directory to produce a set of conventional commits
  • Output ready-to-use git commit commands, which you can copy-paste into your workflow.

Frequently Asked Questions about Conventional Commit Generator

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

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

Generate conventional commit messages by scanning your git working directory to analyze staged and unstaged changes, grouping related modifications by type and scope to produce structured commit messages.

Can I group multiple modified files into a single conventional commit by scope?

Yes, you can group related modifications by logical feature and scope. The tool detects modified files and groups them to produce multiple structured conventional commits for your repository state.

Does this tool support generating breaking-change footers for conventional commits?

Yes, the tool supports generating conventional commits with optional bodies and breaking-change footers, adhering to the Conventional Commits specification to ensure deterministic versioning and cleaner changelogs.

What is the best way to create ready-to-run git commit commands for automated pipelines?

Produce ready-to-run git commit commands by analyzing your repository's diff and staging status. The tool outputs ready-to-use commands that you can copy-paste directly into your automated workflows.

Do I need to stage my files before generating conventional commit messages?

No, you do not need to stage files beforehand. The tool operates across both staged and unstaged changes, analyzing the repository's diff and staging status to generate the commit messages.

Why use a conventional commit generator instead of writing commit messages manually?

Using a conventional commit generator standardizes scattered code changes into structured messages, enabling cleaner changelogs, easier code reviews, and deterministic versioning without manual formatting effort.