What problem does it solve?
Developers often accumulate mixed or noisy changes that make repository history hard to read and review; this Skill guides the creation of logical, focused git commits by inspecting the working tree, diffs, and recent commit patterns to propose clear commit groupings and messages.
Core Features & Use Cases
- Guided Review Workflow: Runs git status, diffs, and recent commit history to recommend which files should be grouped together.
- Commit Strategy & Messaging: Encourages angular-style messages (feat:, fix:, docs:, etc.) and focuses on explaining why changes were made.
- Interactive Clarification: Prompts the user when the intent of changes or the provided hint is ambiguous, and avoids committing debug or unrelated files.
- PR Awareness: Checks for existing pull requests and updates or aligns commit strategy with PR titles and bodies when applicable.
- Use Case: Preparing a clean set of commits for a feature branch before opening or updating a pull request so reviewers can understand intent and scope.
Quick Start
Commit the current outstanding changes into logical, focused commits guided by the hint "commit only documentation and formatting" and ask me before committing any unclear edits.