semantic-git

Atomic conventional commits group related changes and enforce standardized types like feat or fix. This skill formats your changes into an atomic commit and outputs the exact git commands to run for transparent execution.

Atomic staging groups related changes together into a single commit before execution. This approach keeps git history clean and reviewable by ensuring each commit represents one logical change, guided by conventional commit types like feat, fix, or docs.

Yes, you can review plain git commands before execution. The skill outputs explicit git commands for manual review and asks for user confirmation prior to applying any changes, ensuring safe integration with your workflow.

Enforcing conventional commit types standardizes history by requiring prefixes like feat, fix, or docs. This skill guides commits with explicit commands and enforces these types during feature work, bug fixes, and documentation updates.

Yes, the workflow operates without external dependencies. It requires no additional libraries, using plain git commands and user confirmation to automate standardized commits safely within your existing environment.

You should avoid automated conventional commits when changes are unrelated and cannot be grouped atomically. The skill enforces atomic staging, so non-atomic or mixed-scope changes require manual separation before processing.