Git Commit Helper

Analyze staged git diffs to generate conventional-commit compliant messages.

77|9|Updated Oct 10, 2025

Search Tags:#automation #git #developer tools #code review #version control #commit

Ready to run

npx skills add https://github.com/henkisdabro/claudecode-marketplace --skill git-commit-helper-henkisdabro

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Git Commit Helper
Source: https://github.com/henkisdabro/claudecode-marketplace/tree/main/skills/git-commit-helper
Command: npx skills add https://github.com/henkisdabro/claudecode-marketplace --skill git-commit-helper-henkisdabro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing clear, concise, and conventional Git commit messages can be a struggle, leading to inconsistent history and difficult code reviews. This skill streamlines the process by analyzing your changes and suggesting well-structured messages.

Core Features & Use Cases

Automated Message Generation: Analyzes git diffs to suggest commit messages following conventional commit standards.
Conventional Commit Guidance: Provides guidelines and examples for feat, fix, refactor, and other commit types.
Use Case: After staging changes, a developer can ask the AI to "generate a commit message for my staged changes," receiving a formatted suggestion that adheres to team standards.

Quick Start

Generate a descriptive commit message for my currently staged changes.

Frequently Asked Questions about Git Commit Helper

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

FAQPage Schema

How do I generate a conventional commit message from my staged changes?▼

Conventional commit messages follow a structured format with type, scope, and subject. Stage your changes with `git add`, then ask the Skill to analyze your diff and generate a message adhering to conventional commit standards like `feat(scope): description` or `fix: resolve issue`.

What are conventional commits and why should I use them?▼

Conventional commits are a standardized format for Git messages that specify type (feat, fix, docs, refactor, test, chore, style), scope, and description. They improve code review clarity, enable automated changelog generation, and maintain consistent version control history across frontend, backend, docs, and infrastructure.

Can I use this for multi-file commits?▼

Yes, the Skill handles both single-file and multi-file commits. It analyzes staged diffs across all changed files to surface relevant type, scope, and descriptions, then suggests a compliant message that covers all modifications.

How do I amend a commit message after creation?▼

The Skill supports interactive workflow and amend operations. After generating an initial message, you can request modifications to refine type, scope, subject length (under 50 characters), imperative mood, or add breaking-change notes before finalizing.

What commit types does this Skill support?▼

The Skill enforces conventional commit types: `feat` for features, `fix` for bug fixes, `docs` for documentation, `style` for formatting, `refactor` for code restructuring, `test` for test additions, and `chore` for maintenance tasks, with optional breaking-change notation.

Does this work with infrastructure and documentation changes?▼

Yes, the Skill applies across frontend, backend, docs, and infrastructure diffs. It analyzes changes in any domain to determine appropriate type and scope, then generates messages that comply with conventional commit guidelines for mixed-change commits.