gcm

Generate Conventional Commits messages from staged git changes.

1|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/takuan-osho/ccmarketplace --skill gcm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gcm
Source: https://github.com/takuan-osho/ccmarketplace/tree/main/plugins/gcm
Command: npx skills add https://github.com/takuan-osho/ccmarketplace --skill gcm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation of clear, conventional-commits compliant commit messages from your staged changes, reducing manual drafting time and inconsistencies.

Core Features & Use Cases

  • Automatic analysis of staged changes (git diff --cached) to infer the appropriate Conventional Commits type.
  • Generation of a concise subject line (max 50 characters) plus an optional detailed body explaining what and why.
  • References recent commit history for style consistency.

Quick Start

Run the gcm command after staging changes to generate a compliant commit message.

Frequently Asked Questions about gcm

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

FAQPage Schema
How do I auto-generate Git commit messages from staged changes?

You can auto-generate Git commit messages by running the gcm command after staging changes. It analyzes your git diff --cached output to suggest an appropriate Conventional Commits type and message automatically.

What is the conventional commits format for an automated commit message subject line?

The Conventional Commits format requires a proper type prefix followed by a concise subject line limited to 50 characters. The automation tool infers the correct type and generates this standardized message structure.

Can I generate a detailed commit message body explaining what and why changes were made?

Yes, the Git commit message generator provides an optional detailed body following Conventional Commits guidelines. This body explains what changes were made and why, ensuring clear development workflow documentation.

Does the automated commit message generation match my existing repository's style?

Yes, the automated commit message generation references recent commit history for style consistency. This ensures the suggested Conventional Commits messages align with your repository's existing development workflow patterns.

What are the limitations of automating Conventional Commits messages for code quality?

The automation relies on parsing git diff --cached output to infer commit types. Limitations include potential inaccuracies in complex staged changes where the appropriate Conventional Commits type is ambiguous or requires human judgment.