What problem does it solve? Writing good commit messages and splitting mixed staged, unstaged, and untracked changes into clean atomic commits is error-prone: unrelated work gets absorbed, breaking changes go unmarked, and secrets slip into history. This Skill produces a read-only commit plan and complete Conventional Commits messages without touching the repository. ## Core Features & Use Cases - Atomic Commit Splitting: Groups changes by coherent purpose and dependency, assigns every path or hunk exactly once, and never merges independent concerns to hit a numeric limit. - Conventional Commits Drafting: Selects types from repository conventions and confirmed intent, marks breaking changes with ! or a BREAKING CHANGE: footer, and respects repository or user summary-language rules. - Safety Boundaries: Distinguishes staged, unstaged, untracked, partially staged, and supplied-only diffs; redacts suspected secrets; emits candidate commands only when repository state is verified and paths can be quoted safely. - Use Case: You have a staged fix and an unstaged refactor in the same file. Ask for a staged-only commit plan and receive a fix message covering only the staged hunks, with the unstaged work explicitly excluded and no git add proposed. ## Quick Start Ask the agent to draft an atomic commit plan and Conventional Commits message for your staged changes while keeping all unstaged and untracked work out of the plan.