committing-changes

To group uncommitted git changes into logical commits, this Skill analyzes your working directory and clusters related file modifications into distinct, meaningful commit groupings. It then presents each proposed commit for your explicit review and approval before finalizing the version control update.

Resolving merge conflicts interactively during a remote sync requires context from recent local and remote history. This Skill provides that context for each conflict and ensures no resolution is applied without your explicit user confirmation, keeping version control synchronization safe.

This Skill does not automatically push commits to the remote repository. Remote sync is an optional step that occurs only after you have reviewed and approved the logical commit groupings, ensuring you maintain explicit control over version control updates.

You can review and approve code changes before they are committed. The Skill walks you through each proposed logical grouping of uncommitted modifications, requiring your explicit approval for every commit to ensure your version control history tells a clear story.

To organize scattered code changes after a long coding session, this Skill categorizes mixed modifications into logical groups like feature commits, bug fixes, and refactors. It transforms messy working directory states into a clean, structured commit history.

If you do not approve a proposed commit grouping, the Skill will not finalize that specific commit. It facilitates interactive approval, meaning uncommitted changes remain in your working directory until you explicitly accept the proposed version control organization.