git-commit-helper

Generate conventional commit messages from staged git diff changes.

763|165|Updated Sep 16, 2025
One-click install
npx skills add https://github.com/alirezarezvani/claude-code-tresor --skill git-commit-helper-alirezarezvani
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit-helper
Source: https://github.com/alirezarezvani/claude-code-tresor/tree/main/skills/development/git-commit-helper
Command: npx skills add https://github.com/alirezarezvani/claude-code-tresor --skill git-commit-helper-alirezarezvani

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the mental overhead of crafting perfect Git commit messages by automatically generating conventional commit messages based on your staged changes. It ensures consistency, improves project history readability, and saves you time during the commit process.

Core Features & Use Cases

  • Conventional Commit Format: Automatically generates type(scope): subject messages with detailed bodies and issue references.
  • Intelligent Analysis: Analyzes git diff --staged to determine the appropriate commit type (feat, fix, docs, refactor, etc.) and scope.
  • Use Case: After implementing a new authentication feature and staging your changes (git add auth.service.ts login.component.tsx), the skill suggests a commit message like feat(auth): add JWT-based user authentication with a detailed body and issue reference.

Quick Start

The skill activates automatically when you run 'git commit' without a message.

Make some changes and stage them:

git add new-feature.js git commit

The skill will then suggest a conventional commit message for you.

Frequently Asked Questions about git-commit-helper

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

FAQPage Schema
How do I automatically generate conventional commit messages from my staged changes?

Conventional commits automatically generate commit messages by analyzing your staged changes with `git diff`. The Skill determines the commit type (feat, fix, docs, refactor, etc.), extracts scope, formats the subject line, and includes a detailed body with issue references following the conventional commits specification.

What is the conventional commits format and why should I use it?

Conventional commits follow a `type(scope): subject` structure with detailed bodies and footers. This standardized format improves project history readability, enables automated changelog generation, and ensures consistency across your team's version control workflow.

Can I use this Skill with pre-commit hooks in my Git workflow?

Yes, the Skill integrates with pre-commit hooks and review workflows. It activates automatically when you run `git commit` without a message, analyzing staged changes and suggesting a formatted conventional commit message before you finalize the commit.

How does the Skill determine which commit type to assign?

The Skill intelligently analyzes your `git diff --staged` output to identify the nature of changes and assign the appropriate type—such as feat for new features, fix for bug fixes, docs for documentation, or refactor for code restructuring—based on the modifications detected.

Do I need to manually write commit message bodies and footers?

No, the Skill automatically generates detailed bodies and optional footer references based on your staged changes. You receive a complete conventional commit message that follows the specification, eliminating manual formatting and ensuring consistency.

What commit types does this Skill support?

The Skill supports all standard conventional commit types: feat, fix, docs, style, refactor, perf, test, build, ci, and chore. It analyzes your changes to select the appropriate type and extracts scope information for the commit message.