commit-atomic

# Atomic Commit with Logical Grouping Create atomic commits by logically grouping changes following the commitizen/conventional commits convention. Each commit should represent one logical change with a clear, informative message explaining the **what** and **why**. ## Usage ```bash /commit-atomic ``` ## Process ### 1. Inspect the current changes ```bash git status git diff --staged git diff ``` Review all modified, added, and deleted files to understand the full scope of changes. ### 2. Group changes logically Analyze the changes and group them into **logical, independent units**. Each group should: - Address a single concern or feature - Be independently understandable - Not break the build or tests on its own - Follow the dependency order (low-level to high-level) **Grouping strategies:** - By feature or concern (e.g., authentication, UI, database) - By type (e.g., refactoring, bug fix, new feature) - By layer (e.g., model, service, controller) ### 3. Stage each group intentionally **Never use `git add -A` or `git add --all`.** Instead, stage files explicitly: ```bash # Stage specific files git add <file1> <file2> # Stage specific hunks interactively git add -p <file> # Verify what is staged before committing git diff --staged ``` ### 4. Commit each group with a commitizen message Follow the **commitizen conventional commits** format: ```text <type>(<scope>): <subject> [optional body] [optional footer] ``` **Types:** | Type | When to use ...