committing-changes

To organize repository changes into logical git commits, this skill generates a comprehensive commit plan that groups affected files by feature or change type. It presents the proposed structure and awaits your explicit approval before executing any git add or git commit operations.

To enforce explicit user approval for pre-commit staging in automated pipelines, this skill requires strict confirmation prior to any git action. It prevents accidental commits by acting as an auditable, user-driven workflow gatekeeper, even when triggered by orchestrators.

To format git commit messages to follow Chris Beams' seven rules, this skill automatically enforces these standards within its generated commit plan. It structures the proposed messages according to the rules before presenting them for your final review and approval.

The best way to prevent accidental or undesired commits during code collaboration is to use a plan-driven approach that separates staging from execution. This skill provides an auditable workflow by listing affected files and proposed messages, requiring confirmation to prevent unintended changes.

Yes, this commit planning workflow works with your existing version control process by handling typical staging, reviewing, and pushing workflows. It integrates into your development cycle by grouping files into cohesive units and applying strict pre-commit approval gates.