skills.rest
mkitt
mkittCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit-groups

Analyze uncommitted Git changes to propose logical commit groupings.

6|3|Updated Oct 1, 2016
Search Tags:#git#version control#development workflow#commit#staging#code organization
One-click install
npx skills add https://github.com/mkitt/dotfiles --skill commit-groups
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-groups
Source: https://github.com/mkitt/dotfiles/tree/main/claude/skills/commit-groups
Command: npx skills add https://github.com/mkitt/dotfiles --skill commit-groups

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers create more atomic and coherent Git commits by analyzing uncommitted changes and proposing logical groupings.

Core Features & Use Cases

  • Change Analysis: Reviews git status, git diff, and git diff --cached to understand all modifications.
  • Logical Grouping: Identifies natural groupings based on shared purpose, logical coupling, and dependency order.
  • Outline Generation: Presents a structured outline of proposed commit groups and the files/chunks they contain.
  • Use Case: Before committing a large feature, use this Skill to break down the changes into smaller, manageable commits like "Implement user authentication," "Add profile editing UI," and "Update database schema."

Quick Start

Use the commit-groups skill to analyze my current git changes and suggest commit groups.

Frequently Asked Questions about commit-groups

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

FAQPage Schema
How do I organize uncommitted Git changes into logical commit groups?▼

To organize uncommitted Git changes, this Skill analyzes `git status` and unstaged diffs to propose logical groupings for atomic commits based on shared purpose and dependency order.

What is the best way to break down a large feature into atomic Git commits?▼

The best way to break down a large feature into atomic Git commits is to analyze modifications and stage specific files or hunks into coherent commit units grouped by their logical purpose.

Can I group staged and unstaged file diffs by purpose for version control?▼

Yes, you can group staged and unstaged file diffs by purpose for version control. The Skill reviews both `git diff` and `git diff --cached` to identify natural groupings and dependency order.

How does analyzing uncommitted changes help create a structured commit history?▼

Analyzing uncommitted changes helps create a structured commit history by identifying modifications across files and proposing an outline of coherent commit units, ensuring logical coupling and clear development workflow.

Do I need any external dependencies to analyze my Git staging area for code organization?▼

You do not need any external dependencies to analyze your Git staging area for code organization. The Skill operates directly within Git repositories to identify modifications and propose commit units.

Related Skills

Explore More Software Engineering Skills→
zbruhnkezbruhnke
16

code-review

Review Git code changes for correctness, security, performance, and maintainability.

Community
Intermediate
mikanfactorymikanfactory

commit

Analyze Git changes and generate descriptive atomic commit messages.

Community
Intermediate
jls42jls42
1

helping-with-commits

Create Conventional Commits with project scopes and pre-commit validation.

Community
Intermediate
JavierLianoRiozJavierLianoRioz
3

git-commit

Generate conventional Git commit messages from code diffs with intelligent file staging.

Community
Intermediate