Plan and compose well-structured git commits with imperative messages.
npx skills add https://github.com/adrielp/ai-engineering-harness --skill commit-adrielp
Please help me install this Agent Skill. Skill: commit Source: https://github.com/adrielp/ai-engineering-harness/tree/main/gemini/skills/commit Command: npx skills add https://github.com/adrielp/ai-engineering-harness --skill commit-adrielp
Create well-structured git commits for changes made during a session, improving traceability and reviewability of work.
Plan and create clear, atomic commits for session changes using Gemini CLI.
High-intent search queries and answers about installing and using this skill.
To write clear git commit messages, group related code and configuration diffs into logical units, then draft imperative statements that accurately describe the intent and scope of each change.
The best way to group code diffs is to plan commits by identifying related changes across code, docs, and configuration files, organizing them into logical, atomic units that clearly explain session work.
Creating atomic git commits involves splitting session changes into logical groups, drafting concise imperative commit messages for each group, and enforcing staging best practices to separate code and documentation updates.
Yes, you can use Gemini CLI to plan and compose conventional commits, applying guardrails to structure staging and generate imperative commit messages that are ready for execution.
Using imperative mood for git commit messages follows conventional best practices, providing clear, direct instructions that accurately reflect the intent of your code and configuration changes for better traceability.
mkittAnalyze uncommitted Git changes to propose logical commit groupings.
POWERFULMOVESStage, commit, and push Git changes with conventional commit messages.
Tony363Automate Git operations with Conventional Commits and MCP integrations.
74nu5Generate conventional commit messages from diffs and stage files.
