What problem does it solve? Messy working directories often mix features, fixes, docs, and version bumps together, making it hard to create clean, reviewable Git history without accidentally committing unrelated changes or losing user work. ## Core Features & Use Cases - Logical Change Grouping: Reads git status, staged and unstaged diffs, and recent history to group changes by purpose (feature, test, docs, release) rather than by folder. - Conventional Commits: Produces one-purpose commits with compliant titles such as feat:, fix:, docs:, and chore(release):. - Safe Staging and Verification: Uses explicit file paths or interactive patch staging instead of git add ., runs minimal per-group validation, and never amends, rebases, tags, or pushes without explicit user request. - Use Case: After a long coding session with mixed edits across source, tests, and docs, ask the agent to split everything into a clean sequence of reviewable local commits. ## Quick Start Ask the agent to split the current workspace changes into separate Conventional Commits while keeping unrelated edits untouched.