git-commit-assistant

Generate conventional git commit messages and execute them after user approval.

109|40|Updated Jul 24, 2017

Search Tags:#automation #git #workflow #commit #code-quality #version-control #conventional-commits

Ready to run

npx skills add https://github.com/dmitriiweb/extract-emails --skill git-commit-assistant-dmitriiweb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit-assistant
Source: https://github.com/dmitriiweb/extract-emails/tree/main/.codex/skills/git-commit-assistant
Command: npx skills add https://github.com/dmitriiweb/extract-emails --skill git-commit-assistant-dmitriiweb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generate consistent, high-quality conventional git commit messages and, with user approval, execute the commit to maintain clean project histories.

Core Features & Use Cases

Generate conventional commits that follow the standard format (type, optional scope, and a concise imperative summary) with optional body and footers.
Validate the staged changes against conventional rules, guiding split or refinement to ensure a single cohesive change per commit.
Review the generated message and require user approval before performing the commit to avoid noisy histories.

Quick Start

Review staged changes, draft a compliant commit message, then approve to perform the commit.

Frequently Asked Questions about git-commit-assistant

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate conventional commits automatically from staged changes?▼

To generate conventional commits automatically, the Skill reviews your staged changes and drafts a compliant message with the correct type, optional scope, and a 50-72 character summary. You then review and approve the message before the commit executes.

What is the conventional commit format for git version control?▼

The conventional commit format requires a type, an optional scope, and a concise imperative summary of 50-72 characters, optionally followed by a body and footers. This Skill validates your staged changes against these rules to ensure a clean project history.

Can I review and edit a generated commit message before applying it to git?▼

Yes, you can review the generated commit message before applying it. The Skill includes an explicit approval gate that shows the drafted conventional commit message and requires your confirmation to prevent noisy git histories.

How do I split or refine staged changes for a single cohesive git commit?▼

To split or refine staged changes for a single cohesive commit, the Skill validates your changes against conventional rules and guides the refinement process. This ensures each commit represents a single logical change before you approve the final message.

Does this conventional commit generator work without external dependencies?▼

Yes, the conventional commit generator works without external dependencies. It operates independently to analyze your staged changes, draft the commit message using standard conventional-format rules, and present it for your approval.