git-commit

Generate Conventional Commits messages from git diffs.

1|1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/gaoqiongxie/skills-ai --skill git-commit-gaoqiongxie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/gaoqiongxie/skills-ai/tree/main/git-commit
Command: npx skills add https://github.com/gaoqiongxie/skills-ai --skill git-commit-gaoqiongxie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often write vague, non-standard Git commit messages like "fix bug" or "update" that make it difficult to track code changes, debug issues, and collaborate effectively with team members.

Core Features & Use Cases

  • Conventional Commits Support: Generates commit messages following the standard format with all common types (feat, fix, docs, refactor, etc.) and optional scope labels.
  • Scenario Templates: Provides pre-built templates for common change types including bug fixes, new feature additions, code refactors, and documentation updates.
  • Use Case: A developer who just fixed a payment processing bug can paste their git diff to get a properly formatted commit message that clearly describes the change, making future code reviews and rollbacks much easier.

Quick Start

Paste your git diff output into the AI and request a standardized Git commit message following the Conventional Commits format.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate a conventional commit message from a git diff?

To generate a conventional commit message from a git diff, paste the raw code change diff into the tool. It analyzes the changes and outputs a structured message with appropriate type labels, scopes, and subject lines aligned with the Conventional Commits specification.

What is the conventional commits format for bug fixes and new features?

The conventional commits format for bug fixes and features uses structured type labels like feat and fix, optional scopes, and descriptive subject lines. This standardizes codebase changes, making future tracking, debugging, and team collaboration significantly easier.

Can I automatically create scoped git commit messages for code refactors?

Yes, you can automatically create scoped git commit messages for code refactors. The tool provides scenario templates that analyze your diff and apply the correct refactor type label, scope, and description without manual formatting.

How do I write better git commit messages for documentation updates?

To write better git commit messages for documentation updates, input your code diff to apply the docs type label automatically. This ensures your documentation changes follow the conventional commits standard, improving project maintainability.

Does this tool work with raw code change diffs for any git repository?

Yes, this tool works with raw code change diffs from any git repository. It requires no specific dependencies or environment setup, instantly converting pasted diff output into compliant conventional commit messages.