What problem does it solve? Committing a mixed working tree as one blob produces unclear history and skips review. This Skill enforces a disciplined commit workflow: confirm explicit user consent, review the full change set, split changes into logical commits, and write conventional messages for each. ## Core Features & Use Cases - Consent and review gate: Commits only after explicit user intent and a change-tier review, with a local review loop until the verdict is clean or explicitly skipped. - Logical commit splitting: Partitions staged and unstaged changes into self-contained commits ordered by dependency, staging only the paths that belong to each group. - Conventional messages: Uses PR-title prefixes like feat: and fix: with HEREDOC-based commit commands, and never amends rejected commits. - Use Case: After a session that touched a feature, its tests, and an unrelated dependency bump, ask to commit and get three ordered commits with clear imperative messages instead of one mixed dump. ## Quick Start Ask the agent to commit the current working tree and it will review the changes, plan a logical split, and create each conventional commit in order.
