Atomic Commit

To split mixed git changes into atomic commits, this Skill analyzes your working directory and detects mixed concerns, then groups related files into single-purpose commits. It enforces a one-thing-per-commit discipline to ensure each commit is independently revertible.

An atomic commit in version control captures a single, cohesive change that addresses one feature, fix, or refactor. This prevents mixed concerns and broken history, ensuring the commit can be rolled back without affecting other changes.

You can group files for conventional commits automatically by using this Skill to analyze your current changes. It provides conventional commit-ready groups with clear labeling, ensuring the codebase remains buildable.

Yes, atomic committing works with non-TDD development workflows. This Skill provides a repeatable process that can be adopted in manual development workflows where changes span multiple features or fixes.

To verify your git log has clean, single-purpose commits, this Skill supports final verification through git log checks. It validates that the codebase remains buildable and ensures each commit is independently revertible.

You should enforce one-thing-per-commit in your git workflow to eliminate manual fragmentation and prevent mixed concerns. This discipline ensures each commit is independently revertible, keeping your version control history clean and cohesive.