Verified:GitHub

commit

Generate standardized commit messages conforming to the Conventional Commits format with optional scope and breaking-change annotations.

3|Updated Jan 6, 2026

Search Tags:#git #workflow #commit #scope #breaking-changes #semantics #conventional-commits

Ready to run

npx skills add https://github.com/trancong12102/ccc --skill commit-trancong12102

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/trancong12102/ccc/tree/main/core/skills/commit
Command: npx skills add https://github.com/trancong12102/ccc --skill commit-trancong12102

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional commits enforce a standardized, readable history and tooling automation by requiring types like feat or fix, optional scope, and optional breaking change annotations when committing code.

Core Features & Use Cases

Generate standardized commit messages that follow the Conventional Commits specification (types like feat, fix, etc.) with optional scope and breaking-change markers.
Assist in drafting commits during development and release workflows, ensuring consistency across a codebase.
Use cases include preparing releases, automating changelog generation, and validating messages before push.

Quick Start

Ask the AI to generate a commit message for the current changes using the Conventional Commits format.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I generate conventional commit messages for my code changes?▼

You generate conventional commit messages by applying standardized types like feat or fix, optional scope, and breaking-change annotations to your code changes. This enforces a readable history and supports tooling automation.

What is the conventional commits format and when do I need it?▼

The conventional commits format standardizes commit history by requiring types, optional scope, and breaking-change markers. You need it to enforce a readable git history and enable automated changelog generation and release preparation.

How do I indicate breaking changes in a conventional commit?▼

Indicate breaking changes in a conventional commit by adding breaking-change annotations to the message. The format supports optional scope and footer references to provide context for the code changes.

Can I use conventional commits for automating changelog generation?▼

Yes, you can use conventional commits for automating changelog generation. Enforcing standardized types and breaking-change annotations allows tooling to parse git history and generate release notes.

What is the best way to maintain a consistent git workflow for feature work and bug fixes?▼

Maintain a consistent git workflow by generating conventional commit messages for feature work and bug fixes. This ensures consistency across your codebase and standardizes development and release workflows.

Does the conventional commits format support footer references in commit messages?▼

Yes, the conventional commits format supports footer references in commit messages. Along with types and optional scope, footer references allow you to link code changes to external tracking items.