skills.rest
pipemind-com
pipemind-comOFFICIAL
Explore all skills by this author →
WebsiteGitHub

git-commit-changes

Split uncommitted git working-tree changes into numbered atomic commits with conventional messages.

Updated Jan 23, 2026
Search Tags:#git#changelog#commit#code-quality#developer-tools#atomic-commits#version-control
One-click install
npx skills add https://github.com/pipemind-com/pipemind-marketplace --skill git-commit-changes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-changes
Source: https://github.com/pipemind-com/pipemind-marketplace/tree/main/plugins/spec-driven-development/skills/git-commit-changes
Command: npx skills add https://github.com/pipemind-com/pipemind-marketplace --skill git-commit-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers and reviewers struggle with large, mixed-change working trees that make history noisy, hard to review, and difficult to bisect. This Skill analyzes staged, unstaged, and untracked changes and breaks them into a sequence of small, logically grouped commits to create a clean, meaningful git history.

Core Features & Use Cases

  • Change discovery: Runs git status, git diff, and git diff --cached to enumerate staged, unstaged, and untracked modifications.
  • Logical grouping: Groups edits by concern, feature, type, or chore using clear heuristics to form atomic commit units.
  • Safe execution: Produces a numbered commit plan, waits for operator approval, stages specific files or hunks, commits with conventional types and concise messages, and verifies the result with git log.
  • Use case: When you finish work across multiple files and want to produce a review-friendly series of commits (feat, fix, refactor) without pushing or amending existing history.

Quick Start

Analyze the current repository and split all uncommitted changes into a numbered plan of atomic commits, then create those commits locally using conventional commit messages.

Frequently Asked Questions about git-commit-changes

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

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

To split uncommitted git changes, the tool analyzes staged, unstaged, and untracked files, groups them logically by concern, and creates a numbered plan of atomic commits with conventional messages.

What is the best way to group messy working tree changes for a code review?▼

The best way to group messy changes for code review is applying heuristics to separate edits by feature, type, or chore, forming small, review-friendly conventional commits without pushing history.

Can I stage specific file hunks to create conventional commit messages?▼

Yes, you can stage specific files or hunks to create conventional commit messages, allowing you to isolate distinct modifications and generate concise, logically grouped commit units locally.

Does this approach modify or push existing git history?▼

No, this approach does not amend or push existing git history; it safely sequences new local commits from your current working tree and verifies the final result using git log.

When do I need to split git changes into multiple commits?▼

You need to split git changes into multiple commits when preparing code for review or bisecting, ensuring a noisy working tree with mixed modifications becomes a clean, meaningful history.

Related Skills

Explore More Software Engineering Skills→
whatevertogowhatevertogo

git-commit

Generate standardized Git commit messages from staged and working tree changes.

Community
Intermediate
AstrumonAstrumon

changelog-generator

Generate Keep a Changelog entries from Conventional Commits history.

Community
Intermediate
MolcajeteAIMolcajeteAI
2

pre-commit-hooks

Configure Husky and lint-staged pre-commit hooks for automated code quality checks.

Official
Intermediate
mattstrublemattstruble
2

git-commit

Analyze git history and staged changes to craft conventional commit messages.

Community
Advanced