split-commit

Group Git working-tree changes by concern and commit them sequentially.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/spandios/vibe-utils --skill split-commit-spandios
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: split-commit
Source: https://github.com/spandios/vibe-utils/tree/main/skills/split-commit
Command: npx skills add https://github.com/spandios/vibe-utils --skill split-commit-spandios

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps manage large, unwieldy Git commits by breaking them down into smaller, more focused, and logical commits, improving code review clarity and maintainability.

Core Features & Use Cases

  • Intelligent Grouping: Organizes changes by concern (features, tests, config, docs) rather than just file count.
  • Sequential Committing: Stages and commits each logical group in order, ensuring a clean history.
  • User Confirmation: Presents a clear commit plan for user approval before execution.
  • Use Case: You've made significant changes across multiple features and want to commit them, but a single commit would be too large. This Skill helps you split them into individual commits for each feature.

Quick Start

Use the split-commit skill to break down my current large working-tree changes into several smaller, logical commits.

Frequently Asked Questions about split-commit

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

FAQPage Schema
How do I split a large git commit into smaller logical commits?

You split a large git commit by grouping working-tree changes into logical concerns, proposing a commit plan, and executing sequential git add and git commit operations to create focused commits.

How does automatic git commit chunking group my code changes?

Git commit chunking groups oversized working-tree changes by concern, such as features, tests, config, and docs, rather than just splitting files by count, ensuring each commit remains logically focused.

Can I review the commit plan before the Skill executes git add and git commit?

Yes, the Skill presents a clear commit plan for user confirmation before execution, allowing you to review how your working-tree changes are grouped by concern before it runs sequential git add and git commit operations.

Does this tool split commits based on file count or by code concern?

This tool organizes changes by concern, grouping features, tests, config, and docs separately, rather than simply chunking by file count, to maintain a clean and logical version control history.

When should I split my git working-tree changes into multiple commits?

You should split your git working-tree changes when a single commit would be too large or unwieldy, such as after making significant changes across multiple features, to improve code review clarity and maintainability.