git-commit

Generate and execute Conventional Commits with explicit user approval.

Updated Feb 10, 2026

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

Ready to run

npx skills add https://github.com/dustinliu/dot-claude --skill git-commit-dustinliu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/dustinliu/dot-claude/tree/main/my-skills/git-commit
Command: npx skills add https://github.com/dustinliu/dot-claude --skill git-commit-dustinliu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of standardized Git commit messages, ensuring consistency and clarity in your project's version history.

Core Features & Use Cases

Conventional Commits: Generates commit messages following the Conventional Commits specification (type, scope, description).
Interactive Confirmation: Presents a clear summary of staged files and the proposed commit message for user approval before execution.
Change Grouping: Helps split unrelated changes into separate, logical commits.
Use Case: When you've made several distinct changes to your codebase, use this Skill to help you craft individual, well-formatted commit messages for each logical change, rather than one large, messy commit.

Quick Start

Use the git-commit skill to stage and commit the current changes with a conventional commit message.

Frequently Asked Questions about git-commit

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

FAQPage Schema

How do I automate git commit messages using conventional commits?▼

Automate conventional commits by analyzing staged or unstaged git changes, drafting a message with type, scope, and description, and requiring explicit approval before staging and committing. This ensures version control consistency without manual formatting.

What is the best way to split unrelated code changes into separate git commits?▼

Splitting unrelated changes into separate commits involves grouping distinct modifications logically, drafting individual conventional commit messages for each change, and executing them sequentially with user approval to maintain a clean version history.

Can I review the proposed commit message before staging my git changes?▼

Reviewing the proposed commit message before staging is supported through interactive confirmation, which presents a clear summary of staged files and the conventional commit message, requiring explicit user approval before execution.

Does this conventional commit workflow work with unstaged git changes?▼

This conventional commit workflow works with both staged and unstaged git changes. It analyzes the current modifications in your codebase, drafts the appropriate commit message, and stages the files upon your explicit approval.

Why should I use conventional commits for my version control workflow?▼

Conventional commits standardize version history by enforcing a structured format with type, scope, and description. This clarity improves code review processes, automates changelog generation, and ensures consistent communication across project contributions.