commit-message

Generate Conventional Commits messages from the current Git staging area.

24|1|Updated Oct 28, 2025

Search Tags:#automation #git #commit-message #conventional-commits #staged-changes #scope-detection

Ready to run

npx skills add https://github.com/kvet/queuert --skill commit-message-kvet

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers create consistent, conventional commit messages directly from their Git staging area, ensuring standardized history and easier changelog generation.

Core Features & Use Cases

Infer scope from changed files and determine the appropriate commit type (feat, fix, docs, refactor, etc.)
Output a properly formatted Conventional Commits message that can be used by tooling like changesets or semantic-release
Detect breaking changes and append a breaking-change indicator when applicable
Real-world use: stage changes across multiple packages, run the skill, and copy the generated message to the commit command

Quick Start

Stage changes you want to commit, then invoke the skill to generate the conventional commit message. Example: /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 staged changes?▼

You generate a conventional commit message from staged changes by analyzing the Git staging area to infer scope and determine the appropriate type like feat or fix, outputting a properly formatted Conventional Commits message.

How does scope detection work for conventional commits across multiple packages?▼

Scope detection analyzes changed files in your Git staging area to infer the correct scope, ensuring standardized history and easier changelog generation across multiple packages.

Can I automatically detect breaking changes and append them to a conventional commit?▼

Yes, you can detect breaking changes and append a breaking-change indicator to the conventional commit message when applicable to your staged changes.

Does this conventional commit generation approach work with semantic-release and changesets?▼

Yes, the properly formatted Conventional Commits message output is designed to be used by tooling like changesets or semantic-release for automated releases.

What is the best way to automate git commit messages for consistent project history?▼

The best way to automate git commit messages is to infer the type and scope directly from staged changes, creating a standardized conventional commit message without manual formatting.