skills.rest
richardcb
richardcbCOMMUNITY
Explore all skills by this author β†’
GitHub

git-commit

Generate conventional commit messages from staged Git changes.

15|3|Updated Jan 27, 2026
Search Tags:#git#developer tools#version control#commit#conventional commits#code history
One-click install
npx skills add https://github.com/richardcb/oh-my-gemini --skill git-commit-richardcb
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/richardcb/oh-my-gemini/tree/main/skills/git-commit
Command: npx skills add https://github.com/richardcb/oh-my-gemini --skill git-commit-richardcb

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the generation of high-quality, conventional commit messages by analyzing your staged code changes, ensuring a clean and informative git history.

Core Features & Use Cases

  • Automated Commit Message Generation: Analyzes diffs to suggest appropriate commit types (feat, fix, docs, etc.) and scopes.
  • Conventional Commits: Adheres to the conventional commit specification for better tooling and changelog generation.
  • Use Case: After implementing a new feature and fixing a related bug, use this Skill to generate a single, well-structured commit message that accurately reflects both changes and links to the relevant issue.

Quick Start

Use the git-commit skill to generate a commit message for your staged changes.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate conventional commit messages automatically from staged git changes?β–Ό

Automating conventional commit message generation involves analyzing staged git changes to categorize diffs into types like feat, fix, or docs, identifying the scope from modified files, and formatting the subject, body, and footer automatically.

What is the conventional commit format for linking issues and noting breaking changes?β–Ό

The conventional commit format uses a structured message with a subject, body, and footer, where the footer handles issue linking and documents breaking changes to maintain a clean and informative git history.

Can I format git commit types like refactor, perf, and chore automatically?β–Ό

Yes, you can automatically format git commit types like refactor, perf, test, chore, and ci by analyzing code diffs and categorizing staged changes according to the conventional commit specification.

How do I determine the correct scope for a conventional commit from modified files?β–Ό

To determine the correct commit scope from modified files, the generator analyzes the file paths and changes in your staged diff to identify the affected module or component and applies it to the message.

What is the best way to maintain a clean git history when adding features and fixing bugs?β–Ό

The best way to maintain a clean git history is to generate well-structured conventional commit messages that accurately reflect feature additions and bug fixes, ensuring the commit type and scope are correctly categorized.

Related Skills

Explore More Software Engineering Skills→
JeffKMJeffKM

git-commit-skill

Analyze Git changes and generate Korean Conventional Commits messages.

Community
Intermediate
meowgorithmmeowgorithm
34

commit

Analyze git diffs and generate Conventional Commits messages.

Community
Intermediate
dorgonmandorgonman
1

kano-commit-convention-skill

Lint commits against the Kano convention and generate changelogs.

Community
Basic
rserse
44

ase-meta-commit

Generate a concise commit message from `git diff --cached` output.

Community
Basic