micro-commit

Split git diffs into atomic commits with descriptive messages.

558|75|Updated Dec 18, 2025

Search Tags:#automation #git #workflow #commit #diff #version-control #atomic-commit

Ready to run

npx skills add https://github.com/winstonkoh87/Athena-Public --skill micro-commit-winstonkoh87

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: micro-commit
Source: https://github.com/winstonkoh87/Athena-Public/tree/main/examples/skills/coding/micro-commit
Command: npx skills add https://github.com/winstonkoh87/Athena-Public --skill micro-commit-winstonkoh87

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monolithic commits create ambiguous history, hinder rollbacks, and complicate reviews. Atomic commits improve traceability and revertibility.

Core Features & Use Cases

Atomic commits: splits changes into logical blocks aligned with features or fixes.
Automatic staging and committing: each block is committed with a descriptive message.
Multi-file changes: handles changes that span several files within a feature.

Quick Start

Split the current git diff into atomic commits by instructing the assistant to stage and commit each logical block with descriptive messages.

Frequently Asked Questions about micro-commit

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

FAQPage Schema

How do I split a large git commit into smaller atomic commits?▼

Splitting a large git commit into atomic units involves scanning git diff to identify logical blocks, then executing a sequence of git add and git commit commands for each block with descriptive messages to improve traceability.

Why should I use atomic commits instead of monolithic commits in version control?▼

Atomic commits solve the problem of monolithic commits, which create ambiguous history, hinder rollbacks, and complicate reviews. By partitioning changes into logical blocks, atomic commits improve traceability and revertibility across multi-file features.

How do I automatically stage and commit multiple file changes by feature?▼

Automatic staging and committing of multi-file changes is handled by scanning the git diff, identifying logical blocks aligned with features or fixes, and executing git add and git commit commands for each block with descriptive messages.

Can I split changes across multiple files into atomic commits automatically?▼

Yes, the Skill handles multi-file changes by scanning git status and diff to identify logical blocks spanning several files within a feature, then executing git add and git commit commands for each block automatically.

What is the best way to structure git commit history for a large feature implementation?▼

The best way to structure git commit history is to partition code changes into atomic, reviewable units. This involves scanning git diff to identify logical blocks and committing each block individually with descriptive messages for structured history.

Do I need any additional tools or dependencies to partition code changes into atomic commits?▼

No additional tools or dependencies are required to partition code changes into atomic commits. The Skill operates independently by scanning git status and diff, then executing git add and git commit commands for each logical block.