Git Commit Helper

Generate conventional commit messages by analyzing staged git diffs.

Updated Mar 14, 2026

Search Tags:#git #workflow #commit #diff #code-quality #conventional-commits

Ready to run

npx skills add https://github.com/edyruja/ProiectAIDiodele --skill git-commit-helper-edyruja

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Git Commit Helper
Source: https://github.com/edyruja/ProiectAIDiodele/tree/main/.agent/skills/Git%20Commit%20Helper
Command: npx skills add https://github.com/edyruja/ProiectAIDiodele --skill git-commit-helper-edyruja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate descriptive commit messages by analyzing git diffs.

Core Features & Use Cases

Analyze staged changes and produce concise, conventional commit messages that follow the standard format (type(scope): description).
Suggest appropriate types (feat, fix, docs, style, refactor, test, chore) and optional scopes based on the changes.
Provide guidance for including body text and breaking changes when applicable to improve traceability and review.

Quick Start

Analyze staged changes and generate a descriptive conventional commit message.

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 conventional commit messages from a git diff?▼

Analyze your staged git diff to automatically generate descriptive conventional commit messages formatted as type(scope): description. This ensures consistent messaging across features, fixes, docs, and refactors for better traceability.

What is the conventional commits format for structuring git commit messages?▼

The conventional commits format structures git commit messages using a type, optional scope, and description, such as feat(scope): description. It also supports optional body text and breaking-change notes to improve code review and traceability.

How do I write a git commit message for a code refactor or bug fix?▼

To write a git commit message for a code refactor or bug fix, analyze the staged diff to suggest appropriate types like refactor or fix. Include an optional scope and a concise description to categorize the code-quality changes accurately.

Does generating conventional commit messages work for any staged changes in software projects?▼

Generating conventional commit messages applies to reviewing staged changes across software projects of any scale. It analyzes the provided git diff to suggest appropriate types and scopes for consistent messaging without requiring specific dependencies.

How do I indicate breaking changes in a conventional commit message?▼

To indicate breaking changes in a conventional commit message, include optional breaking-change notes within the message body. Analyzing the git diff helps provide guidance on when to add these notes to improve traceability and review.