commit-message

Generate conventional commit messages from git diffs and branch names.

Updated Aug 27, 2026

Search Tags:#git #workflow #staging #commit-message #conventional-commits #diff-analysis #commitizen

Ready to run

npx skills add https://github.com/BearyDevs/dotfiles --skill commit-message-bearydevs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/BearyDevs/dotfiles/tree/main/.config/opencode/skills/commit-message
Command: npx skills add https://github.com/BearyDevs/dotfiles --skill commit-message-bearydevs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates clear, conventional commit messages from git changes by reading the diff and the current branch, ensuring a consistent history and smoother reviews.

Core Features & Use Cases

Automatic type and scope inference from changes to produce a proper Commitizen-style title
Structured body that groups related changes into topics for clarity
Handles staging scenarios, including when nothing is staged, and prompts for review before committing

Quick Start

Describe the changes you staged, and I will generate a polished commit message.

Frequently Asked Questions about commit-message

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, the skill reads your staged changes and current branch name to infer the correct type and scope. It then structures the body by topics to produce a clear Commitizen-style title and body.

How does automatic commit type and scope inference work from staged changes?▼

Automatic commit type and scope inference works by analyzing the content of your git diff. The skill applies Commitizen rules to map the detected changes to the appropriate type and scope, forming a structured title like type(scope): subject.

What happens to commit message generation when nothing is staged in git?▼

When nothing is staged in git, the skill identifies the empty staging area and handles the scenario by prompting you for review before committing. This prevents empty commits and ensures you review changes first.

What is the best way to structure a commit body by topics from a diff?▼

The best way to structure a commit body by topics is to group related changes identified in the diff. This skill automatically categorizes diff sections into concise, topic-based lines for a readable commit history.

Do I need Commitizen installed to format my git commit messages?▼

You do not need Commitizen installed externally to format your git commit messages. The skill applies Commitizen rules internally to generate the conventional commit format directly from your diff and branch name.

Can I use my current branch name to determine the commit scope?▼

Yes, you can use your current branch name to determine the commit scope. The skill reads the branch name alongside the diff to accurately infer the scope and structure the Commitizen-style title.