git_commit_helper

To automate clean git commit messages, this Skill analyzes your git diff and status to group changes logically and draft messages in imperative mood. It presents a commit plan and requires your explicit confirmation before executing the git add and git commit commands.

Grouping file changes into logical git commits involves analyzing the diff to identify related boundaries. This Skill inspects recent history and current changes to plan single or multiple commits, ensuring each commit message includes a clear rationale.

Yes, you can review and approve git commits before execution. The Skill operates with guardrails by presenting a structured commit plan and requiring explicit user confirmation before running any git add or git commit operations via the CLI.

The best way to ensure git commit messages follow imperative mood is to use an automated helper that applies message guidelines during generation. This Skill drafts commit messages in imperative mood and includes the rationale behind the changes.

Yes, the git commit automation works without external dependencies. It operates entirely within the Gemini CLI environment to inspect git history, analyze diffs, and execute commits based on your approved plan.

Using an automated workflow for git commits ensures structured messages and logical grouping by analyzing diffs and recent history. Unlike manual commits, it provides a reviewable plan with guardrails and requires explicit confirmation before executing changes.