git-smart-commit

Split git changes into conventional commits with suggested messages.

Updated Nov 26, 2025
One-click install
npx skills add https://github.com/hmj1026/docker_run --skill git-smart-commit-hmj1026
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-smart-commit
Source: https://github.com/hmj1026/docker_run/tree/main/.gemini/skills/git-smart-commit
Command: npx skills add https://github.com/hmj1026/docker_run --skill git-smart-commit-hmj1026

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

將 git 變更,依功能邏輯自動拆分成多個有意義的 conventional commit,提升版本紀錄的可讀性與可追蹤性。

Core Features & Use Cases

  • 自動分群:根據專案邏輯與修改範圍把變更拆分為多個獨立的 commit 群組
  • 提示與輸出:生成提交計畫與建議的提交訊息,方便重複使用
  • 重用性:適用於包含未 staged 的變更與多次 staged 的情境,保證每個群組具有單一責任
  • Use Case: 當一次修改涉及多個功能時,分別提交以維持清晰的變更紀錄

Quick Start

只需執行 git-smart-commit 的工作流程,自動對變更進行分群並產出提交計畫

Frequently Asked Questions about git-smart-commit

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

FAQPage Schema
How do I split git changes into multiple meaningful commits automatically?▼

Yes, you can generate conventional commit messages for mixed staged and unstaged changes. The Skill analyzes both states, groups edits by feature logic, and outputs a structured commit plan with suggested messages to maintain a single responsibility per commit.

What is the best way to organize multiple feature changes into a reproducible git commit history?▼

Yes, this Skill can analyze both staged and unstaged changes simultaneously. It evaluates your working directory and staged area, groups edits by feature logic, and outputs a comprehensive commit plan with suggested conventional commit messages.

How does automated conventional commit grouping handle complex code organization?▼

Automated conventional commit splitting works by analyzing your git diffs to determine logical groupings. It clusters related file modifications together based on feature logic, ensuring each generated commit message reflects a single functional responsibility.

Do I need to manually stage files before using an automated git commit splitting workflow?▼

No, you do not need to manually stage files beforehand. The workflow evaluates both staged and unstaged changes directly, automatically grouping modifications by feature logic to produce a reusable commit plan with suggested commit messages.

When should I use automated conventional commit splitting for version control?▼

You should use automated conventional commit splitting when a single development session involves multiple feature modifications. It separates these edits into distinct groups, improving version control traceability and changelog clarity for end-to-end workflows.