git-commit-gen

Generate Conventional Commits messages from staged or unstaged diffs.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/sky770825/openclaw-console-hub --skill git-commit-gen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit-gen
Source: https://github.com/sky770825/openclaw-console-hub/tree/main/skills/git-commit-gen
Command: npx skills add https://github.com/sky770825/openclaw-console-hub --skill git-commit-gen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of standardized Git commit messages, ensuring consistency and saving developers time when describing code changes.

Core Features & Use Cases

  • Automatic Type Detection: Intelligently suggests commit types (feat, fix, docs, etc.) based on code changes.
  • Scope Inference: Derives relevant scopes from file paths to provide context.
  • Use Case: After making several changes to a feature module, run this Skill to get a perfectly formatted commit message like feat(auth): implement user login flow without manual effort.

Quick Start

Run the git commit generator script to create a commit message for your staged changes.

Frequently Asked Questions about git-commit-gen

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

FAQPage Schema
How do I automatically generate conventional commit messages from git diffs?

You can generate conventional commit messages by running a script that analyzes your staged or unstaged git diffs. It automatically detects the commit type and scope from file changes to produce a standardized message.

How does automatic commit type and scope detection work for conventional commits?

Automatic type and scope detection works by analyzing file additions, deletions, and path changes in your git diff. It intelligently infers the correct type, like feat or fix, and derives the scope from the affected directories.

Can I output conventional commit messages as JSON for integration with other developer tools?

Yes, you can output conventional commit messages as JSON. This allows you to easily integrate the generated commit data into other automated developer tools and continuous integration pipelines.

Do I need Python3 installed to generate conventional commits from staged changes?

Yes, you need Python3 installed in your environment. It is the required runtime dependency for executing the scripts that analyze your git diffs and generate the commit messages.

What is the best way to apply a generated conventional commit directly without manual effort?

The best way to apply a generated conventional commit directly is by using the script's direct commit application feature. This bypasses manual copying and creates the commit from the diff automatically.

How to write conventional commits for multiple file changes across a feature module?

To write conventional commits for multiple file changes, run the generator against your staged changes. It evaluates all file modifications to suggest a single, properly formatted commit message with the appropriate scope.