work-unit-manager

To create atomic commits, analyze your diffs to identify natural boundaries and group related changes into work units. This skill proposes scoped unit boundaries and guides commit messages to maintain clean history across multiple files and features.

Atomic work units are logically grouped, self-contained change sets that span related files and features. They enforce well-scoped changes to improve commit quality, traceability, code reviews, and rollback capability in collaborative projects.

Diff analysis for commit boundaries evaluates multi-file change sets to detect logical separations between features. The skill applies this analysis to propose scoped work units, ensuring each commit represents a single, well-scoped atomic change.

Yes, grouping changes into atomic work units is designed for large-scale development across multiple files and features. It maintains a clear commit history and enables safer rollbacks during complex, collaborative development tasks.

The best way to group changes for safer rollbacks is to analyze diffs and enforce atomic, well-scoped work units. This ensures commits are self-contained, improving traceability and allowing precise rollback capability if issues arise.