What problem does it solve? Writing clear, consistent git commit messages and deciding how to split changes into atomic commits is tedious and error-prone. This Skill automates the full stage-commit-push flow while enforcing Conventional Commits style and safe git practices. ## Core Features & Use Cases - Atomic Commit Splitting: Analyzes your working tree and splits changes by concern, type, and file pattern so each commit builds and makes sense on its own. - Conventional Commits Messages: Generates terse imperative subjects (≤50 chars) with optional bodies only when the "why" is not obvious, matching your repo's existing style. - Safe Staging and Pushing: Stages files by name (never git add -A), skips potential secret files like .env or *.pem, pushes to the current branch, and never force-pushes. - Use Case: After finishing a feature plus a docs tweak, say "commit and push" and get two clean commits — feat(api): add profile endpoint and docs: update api readme — pushed to origin without touching unrelated files. ## Quick Start Ask the assistant to commit and push my current changes using the commit-push skill.