atomic-commits

Group unstaged changes into atomic commits by logical concern.

12|1|Updated Feb 13, 2026

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

Ready to run

npx skills add https://github.com/helderberto/skills --skill atomic-commits-helderberto

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: atomic-commits
Source: https://github.com/helderberto/skills/tree/main/atomic-commits
Command: npx skills add https://github.com/helderberto/skills --skill atomic-commits-helderberto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Group unstaged and untracked changes into atomic commits, ensuring each commit captures a single logical reason to change and simplifying review and push.

Core Features & Use Cases

Group by concern: cluster related changes into separate commits for focused reviews.
Guided workflow: prompts and checks to stage files selectively and prepare concise, repo-style commit messages.
Use Case: when preparing a feature, a bug fix, or documentation update, you split into separate commits before pushing.

Quick Start

Organize my current unstaged changes into atomic commits, one per logical concern, then push.

Frequently Asked Questions about atomic-commits

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

FAQPage Schema

How do I split unstaged changes into atomic commits by concern?▼

Atomic commits group modifications by logical concern, selectively staging files so each commit represents a single reason to change. This workflow isolates features, bug fixes, or documentation updates into separate commits before pushing to maintain a review-friendly history.

What is the best way to prepare a feature or bug fix for a clean git history?▼

The best way to prepare a feature or bug fix is isolating changes into separate commits before pushing. Selectively stage related files, generate concise repo-style commit messages, and push to enforce a clean, review-friendly version control history.

Can I group untracked and unstaged files into separate commits before pushing?▼

Yes, you can group both untracked and unstaged files into separate commits. The workflow clusters changes by concern, prompting selective staging to ensure each commit captures a single logical reason to change before the final push.

Why use selective staging for version control instead of committing all changes at once?▼

Selective staging for version control ensures each commit captures a single logical reason to change. Committing all changes at once mixes concerns, whereas isolating modifications into separate commits creates a clean, review-friendly history that simplifies code quality analysis.

When do I need to organize my workflow into atomic commits?▼

You need to organize your workflow into atomic commits when preparing a feature, a bug fix, or documentation update. Splitting changes into separate commits before pushing maintains a clean history and simplifies the review process.