git-commit-split

Breaks down git changes into meaningful Conventional Commits by file and hunk.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/furedea/dotfiles --skill git-commit-split
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit-split
Source: https://github.com/furedea/dotfiles/tree/main/agents/skills/git-commit-split
Command: npx skills add https://github.com/furedea/dotfiles --skill git-commit-split

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers break down complex, unorganized git changes into meaningful, independent commits, improving code review and version history clarity.

Core Features & Use Cases

  • Change Grouping: Analyzes unstaged and staged changes, grouping related hunks by intent.
  • Commit Generation: Creates multiple commits with descriptive Conventional Commit messages.
  • Use Case: When a developer has made multiple unrelated adjustments before committing, using this Skill ensures each change is properly isolated for better traceability and review.

Quick Start

Use the git commit split skill to turn your accumulated uncommitted changes into logical commits with descriptive messages.

Frequently Asked Questions about git-commit-split

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

FAQPage Schema
How do I split uncommitted git changes into separate commits?

You can split uncommitted git changes by grouping related hunks by intent and generating multiple commits. This Skill automates that process, taking your mixed modifications and organizing them into isolated, traceable commits with descriptive messages.

What is the best way to organize large git diffs before committing?

The best way to organize large git diffs is to group related hunks by intent and apply Conventional Commit standards. This Skill processes your pending changes to ensure each modification is properly isolated for better version history and review clarity.

Can I split a single git commit by hunks across different files?

Yes, you can split changes by hunks across different files. This Skill supports splitting modifications at the hunk level, enabling precise control over commit granularity so unrelated adjustments within the same file are separated.

Do I need Python to automate splitting git commits into conventional commits?

Yes, you need Python installed to automate splitting git commits. This Skill requires Python scripts for processing your diffs and automatically generating the descriptive Conventional Commit messages for your organized changes.

When do I need to break down accumulated git modifications into separate commits?

You need to break down accumulated git modifications when you have made multiple unrelated adjustments before committing. Splitting these changes ensures each modification is properly isolated, improving project history traceability and code review clarity.