commit-generator

Name: commit-generator
Availability: InStock
Author: Showiix

Generate Conventional Commits messages from Git staged changes.

2|Updated Feb 7, 2026

Search Tags:#automation #git #commit #code-review #version-control #conventional-commits

Ready to run

npx skills add https://github.com/Showiix/EsportManager2 --skill commit-generator-showiix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-generator
Source: https://github.com/Showiix/EsportManager2/tree/main/.claude/skills/commit-generator
Command: npx skills add https://github.com/Showiix/EsportManager2 --skill commit-generator-showiix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill analyzes Git's staged changes to produce standardized commit messages, eliminating guesswork and ensuring consistent history.

Core Features & Use Cases

Conventional Commits: generate messages following the Conventional Commits spec with type, scope, and description.
Staged-Change Analysis: reads git diff --cached and recent history to tailor subject lines.
Use Case: when preparing commits for a project with strict messaging guidelines or code reviews, you can auto-create messages from your staged edits.

Quick Start

Commit a few changes to the index and ask the AI to generate a conventional commit message for them.

Frequently Asked Questions about commit-generator

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

FAQPage Schema

How do I generate conventional commit messages from staged changes?▼

To generate conventional commit messages from staged changes, stage your edits in Git and ask the AI to analyze the diff. The Skill parses git diff --cached to produce a formatted message with type, scope, and description.

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

The conventional commits format standardizes Git history by requiring type prefixes like feat or fix, an optional scope, and a description. You need it for projects with strict messaging guidelines or automated code review workflows.

Does the commit generator work with existing Git history and recent commit context?▼

Yes, the commit generator works with existing Git history by reading recent commits alongside git diff --cached. This context helps tailor the subject line to match your project's ongoing development patterns and messaging style.

Can I include a scope and body in my auto-generated conventional commits?▼

Yes, you can include an optional scope and body in auto-generated conventional commits. The Skill formats messages per the Conventional Commits spec, appending a body to provide additional context for your staged code changes.

What are the limitations of automating commit message generation from a git diff?▼

Automating commit message generation from a git diff relies entirely on the staged content's context. If changes are overly broad or disconnected, the generated type prefix and description may lack the specificity needed for clear version control history.