commit

Generate Conventional Commits messages for git-based code changes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/KosmoCHE/claude-plugins --skill commit-kosmoche
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/KosmoCHE/claude-plugins/tree/main/git-command/skills/commit
Command: npx skills add https://github.com/KosmoCHE/claude-plugins --skill commit-kosmoche

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill helps you generate concise and properly formatted git commits using the Conventional Commits standard, reducing ambiguity and improving changelog clarity.

Core Features & Use Cases

  • Automatic commit message generation: Create type-prefixed messages (feat, fix, docs, etc.) with optional scope based on the changes detected.
  • Format validation: Ensures the subject line follows the Conventional Commits rules and suggests a body or footer when appropriate.
  • Use Case: When preparing a release, generate consistent commit messages across multiple changes to streamline changelog generation.

Quick Start

Craft a single Conventional Commits message describing the changes in this patch.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate a conventional commit message for my git changes?

To generate a conventional commit message, this Skill analyzes your code changes and automatically formats a type-prefixed message with an optional scope and a concise subject line. It validates the output against Conventional Commits rules to ensure proper structure.

What is the conventional commits format for features, fixes, and docs?

The conventional commits format prefixes messages with types like feat, fix, or docs, followed by an optional scope in parentheses and a descriptive subject. This Skill validates these elements to reduce ambiguity and improve changelog clarity.

How do I write a valid conventional commit subject line for a code refactor?

A valid conventional commit subject line for a refactor uses the refactor type prefix followed by a concise description of the changes. This Skill validates the type, scope, and subject against conventional rules and suggests a body or footer when appropriate.

Can I use this to automate commit messages for a git-based release workflow?

Yes, you can use this to automate commit message generation for a git-based release workflow. It creates consistent, type-prefixed messages across multiple changes, which streamlines the changelog generation process during releases.

Do I need to specify the commit scope manually when formatting version control messages?

No, specifying the commit scope is optional when formatting version control messages. The Skill detects changes and generates the message with an optional scope, validating the type, scope, and subject to ensure the final output follows Conventional Commits rules.