git-commit-composer

Group git diff hunks into atomic Conventional Commits.

1|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/UtsavBalar1231/claude-code-configs --skill git-commit-composer-utsavbalar1231
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit-composer
Source: https://github.com/UtsavBalar1231/claude-code-configs/tree/main/skills/git-commit-composer
Command: npx skills add https://github.com/UtsavBalar1231/claude-code-configs --skill git-commit-composer-utsavbalar1231

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes changes, groups hunks into coherent commits, and generates conventional, atomic commit messages, then optionally performs the commits to maintain a clean history.

Core Features & Use Cases

  • Diff analysis: Inspects git diffs to understand changes.
  • Commit grouping: Groups related hunks into single commits.
  • Conventional messages: Creates conventional commit messages with optional scopes and bodies.
  • Atomic commits: Ensures each commit is focused and revertible.
  • Automation flow: Supports automated commits and optional review prompts.

Quick Start

Run the composer on your current repository to generate and apply atomic commits.

Frequently Asked Questions about git-commit-composer

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

FAQPage Schema
How do I automatically create atomic git commits from my code changes?

Atomic commits group related code changes into focused, revertible units. This Skill analyzes your git diff, groups related hunks together, and generates conventional commit messages with type, scope, and description, then applies them to maintain a clean history.

What are conventional commits and why should I use them?

Conventional commits follow a standard format—type, scope, description, body, and footer—making commit history readable and enabling automated changelog generation. This Skill formats your commits in this style automatically, improving code review and project maintainability.

Can this work with repositories that have mixed file types and diverse changes?

Yes. This Skill handles diff analysis and hunk grouping across diverse repositories, supporting features, fixes, docs, tests, refactors, and other change types. It ensures each commit remains isolated and buildable regardless of file structure.

How does commit grouping work—what makes hunks related?

The Skill inspects git diffs to understand changes, then groups related hunks by analyzing their context and purpose. This ensures logically connected modifications—like a function change and its test—stay in the same commit rather than split across multiple commits.

Do I need to review commits before they're applied?

The Skill supports both automated commits and optional review prompts. You can generate and inspect the proposed atomic commits and conventional messages before they're applied to your repository.

What's the benefit of atomic commits over squashing everything into one?

Atomic commits remain focused and revertible, making it easier to isolate bugs, review changes, and revert specific features without affecting unrelated code. This Skill ensures each commit serves a single purpose and can be understood independently.