git-commit

Generate well-formed Git commit messages from staged changes.

6|1|Updated Jun 1, 2025
One-click install
npx skills add https://github.com/rezics/rezics --skill git-commit-rezics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/rezics/rezics/tree/main/.claude/skills/git-commit
Command: npx skills add https://github.com/rezics/rezics --skill git-commit-rezics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing clear and standardized Git commit messages from changes can be tedious and error-prone; this skill automates the process by generating well-formed messages that reflect the diff and align with conventional commit standards.

Core Features & Use Cases

  • Auto-detects the commit type from staged changes but always allows override.
  • Generates concise, descriptive messages for single-file or multi-file diffs, including merge commits.
  • Helps maintain a readable project history by enforcing a consistent messaging style.

Quick Start

Ask the AI to generate a commit message for the currently 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 from staged Git changes?▼

You can generate conventional commit messages by running the git-commit skill against your staged changes. It auto-detects the commit type from the diff and writes a descriptive, standardized message automatically.

Can I override the auto-detected commit type for my Git diff?▼

Yes, you can override the auto-detected commit type. While the skill analyzes staged changes to suggest a conventional commit type, it always allows manual overrides to ensure the final message matches your intent.

What is the best way to handle large multi-file diffs in version control?▼

For large multi-file diffs, the best approach is to split them into separate commits. This skill analyzes the staged changes and suggests breaking down large diffs into multiple, well-formed conventional commit messages.

How do I write consistent merge commit messages?▼

To write consistent merge commit messages, apply this skill to your current changes. It generates concise, descriptive messages for multi-file diffs and merges, enforcing a uniform messaging style for project history.

Does this commit message generator work without any external dependencies?▼

Yes, the commit message generator works without external dependencies. It operates directly on your staged Git changes to produce conventional commit messages without requiring additional components or libraries.