commit

What problem does it solve? Writing clear, consistent git commit messages and deciding how to split large changesets into atomic commits is tedious and error-prone. This Skill automates commit creation with terse, exact Conventional Commits messages while enforcing safe staging 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 imperative subject lines (≤50 chars) with proper types like feat, fix, refactor, and adds bodies only when the why is not obvious, including BREAKING CHANGE footers. - Safe Staging Rules: Stages files by name only, never uses git add -A, and refuses to stage files that may contain secrets like .env, *.key, or credentials.json. - Use Case: After refactoring an API route and updating its tests and docs, ask for a commit and receive three separate commits (refactor, test, docs) each with a properly formatted message matching your project's history style. ## Quick Start Ask the assistant to commit my current changes with atomic Conventional Commits messages.