commit

Generate conventional commit messages for staged and unstaged Git changes.

1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/gihwan-dev/claude-code-gui --skill commit-gihwan-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/gihwan-dev/claude-code-gui/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/gihwan-dev/claude-code-gui --skill commit-gihwan-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams enforce consistent, conventional commit messages across a Git workflow, reducing ambiguity in change history.

Core Features & Use Cases

  • Automatic commit message generation: Create standardized messages based on detected changes and the Conventional Commits spec.
  • Commit splitting & grouping: Analyze diffs to propose multiple atomic commits when different concerns are present.
  • Workflow integration: Works with standard Git commands and Husky hooks to ensure pre-commit checks (and optional skip via --no-verify).

Quick Start

Prompt the AI to generate a conventional commit for the currently staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages automatically for staged git changes?

To generate conventional commit messages, prompt the AI to analyze your staged and unstaged git diffs, automatically detecting logical groupings to propose multiple atomic commits formatted as type(scope): description.

Can I split mixed git changes into multiple atomic commits?

Yes, you can split mixed git changes into multiple atomic commits by analyzing diffs to detect distinct logical groupings, proposing separate conventional commit messages for each detected concern.

Does this conventional commit tool work with Husky pre-commit hooks?

Yes, this conventional commit tool integrates with Husky pre-commit hooks to enforce standardized Git workflow checks, allowing you to optionally skip verifications using the --no-verify flag.

What is the conventional commit format used for generating these messages?

The conventional commit format used is type(scope): [#issue] description. This structure ensures consistent, unambiguous software project change history across teams using Git version control.

Why should I use conventional commits instead of writing custom git messages?

You should use conventional commits to reduce ambiguity in your Git version-control history. Enforcing a standardized format across mixed changes ensures automated tracking and clear, structured project documentation.

Can I generate Korean commit messages for my software project?

Yes, you can generate Korean commit messages. When analyzing your git repository changes and applying the conventional commit format, the tool outputs Korean-language descriptions for your commits.