atomic-commits

Divide working tree changes into logical atomic commits with clear messages.

1|Updated Jan 24, 2026

Search Tags:#git #workflow #commit #code-review #atomic-commits #version-control #change-management

Ready to run

npx skills add https://github.com/Hunt-Gather-Create/_R1 --skill atomic-commits-hunt-gather-create

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: atomic-commits
Source: https://github.com/Hunt-Gather-Create/_R1/tree/main/.claude/skills/atomic-commits
Command: npx skills add https://github.com/Hunt-Gather-Create/_R1 --skill atomic-commits-hunt-gather-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break down the current working tree changes into focused, atomic commits, each with a single purpose and clear message.

Core Features & Use Cases

Group related changes into distinct commits to improve traceability and code review.
Ensure each commit has a coherent intent, simplifying rollback and history navigation.
Use in collaborative workflows to minimize merge conflicts and ambiguity.

Quick Start

Split my current changes into atomic commits by grouping related hunks and writing clear messages.

Frequently Asked Questions about atomic-commits

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

FAQPage Schema

How do I split my working tree changes into atomic commits?▼

Split working tree changes into atomic commits by grouping related git diff hunks and staging them separately. This process ensures each commit represents a single logical change with a clear message, improving traceability and history navigation.

What are atomic commits in git version control?▼

Atomic commits in git are focused, single-purpose commits grouping related changes together. This change management technique ensures each commit has coherent intent, simplifying code review, rollback, and history navigation.

Can I use this to separate staged and unstaged changes across multiple files?▼

Yes, you can separate mixed staged and unstaged changes across multiple files. The workflow analyzes your current git diff to group related hunks, accommodating both refactors and feature work into distinct commits.

Why should I divide my git diff into focused commits for code review?▼

Dividing your git diff into focused commits improves code review by ensuring each commit has coherent intent. This grouping minimizes merge conflicts and ambiguity in collaborative workflows, simplifying rollback.