create-commit-message

Name: create-commit-message
Availability: InStock
Author: GeneralJerel

Generate conventional commit messages from staged git diffs.

6|Updated Feb 19, 2026

Search Tags:#automation #git #commit #tooling #diff #conventional-commits #subject-line

Ready to run

npx skills add https://github.com/GeneralJerel/chalk-skills --skill create-commit-message

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-commit-message
Source: https://github.com/GeneralJerel/chalk-skills/tree/main/skills/create-commit-message
Command: npx skills add https://github.com/GeneralJerel/chalk-skills --skill create-commit-message

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate precise conventional commit messages from staged diffs to remove guesswork and enforce consistency.

Core Features & Use Cases

Classifies change type (feat, fix, docs, etc.) from the diff and infers an appropriate scope based on touched paths.
Enforces subject line length (<= 72 chars) and provides an optional body and footer when necessary.
Supports repository-specific conventions by reading existing commitlint or config files and aligning output accordingly.

Quick Start

Generate a Conventional Commit message for the currently staged changes.

Frequently Asked Questions about create-commit-message

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

FAQPage Schema

How do I generate conventional commit messages from staged git changes?▼

You can generate conventional commit messages by analyzing staged git diffs to determine the change type, infer scope from touched files, and format the subject line to 72 characters with an optional body and footer.

What is a conventional commit message generator and how does it work?▼

A conventional commit message generator analyzes your staged git diff to classify the change type, infers an appropriate scope based on touched paths, and formats the output according to Conventional Commits standards.

Does the tool automatically enforce the 72 character limit for commit subject lines?▼

Yes, the tool enforces subject line length to 72 characters and provides an optional body and footer when necessary to comply with conventional commit formatting.

Can I use my existing commitlint config to align generated commit messages?▼

Yes, the generator respects repository-specific conventions by reading existing commitlint or config files and aligning the output accordingly to match your project standards.

How do I create commit messages for feature branches or hotfix workflows?▼

The generator adapts to various workflows such as feature branches and hotfixes by analyzing the staged diff and inferring the appropriate commit type and scope based on the touched file paths.

What is the best way to automate conventional commits for git diffs?▼

The best way to automate conventional commits is to use a tool that parses your staged git diff, classifies the change type, infers scope from touched files, and formats the message according to your local commitlint configuration.