commit-message

Generate conventional commit messages from staged git changes.

6|1|Updated Mar 25, 2019

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

Ready to run

npx skills add https://github.com/Stephanvs/dotfiles --skill commit-message-stephanvs

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of clean, conventional commit messages from the set of changes you have staged, saving time and reducing inconsistent messages.

Core Features & Use Cases

Check for staged changes: Analyze the git diff --cached to determine what will be committed.
Conventional commit formatting: Generate a message following the conventional commits spec (type(scope): description, with optional body/footers).
Output ready-to-use: Return a message that can be pasted directly into git commit -m or used with -T/ -F.
Use Case: You staged changes to implement a new feature in the auth module; the AI suggests "feat(auth): implement login flow" for a clean, predictable history.

Quick Start

Generate a conventional commit message for the currently staged changes.

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 for staged changes?▼

Conventional commits generate a formatted message from your staged git changes following the spec: type(scope): description with optional body and footer. Stage your changes with git add, then use this Skill to output a ready-to-use message you can paste directly into git commit -m.

What is the conventional commits format and why use it?▼

Conventional commits enforce a structured format (type(scope): description) that makes commit history predictable and machine-readable. Types include feat, fix, docs, style, refactor, and ci. This standardization reduces inconsistent messages and improves project history clarity.

Can I use conventional commits with bash automation?▼

Yes. Conventional commits work with bash scripting and git automation workflows. This Skill analyzes git diff --cached output and generates a message you can pipe into commit commands or save to a file with -F, enabling fully automated commit pipelines.

What happens if I have no staged changes?▼

The Skill checks for staged changes before generating a message. If no changes are staged, it returns no commit message—stage your changes with git add first, then generate the conventional commit message.

Are there character limits for conventional commit messages?▼

Yes. The subject line is limited to 72 characters, enforces imperative mood, and must not end with a period. Optional body and footer sections follow standard conventional commits rules for longer explanations and metadata.

Does this work across all project types and change types?▼

Conventional commits apply to any project using the spec. This Skill handles features, fixes, documentation, styles, refactors, and CI-related updates. It works wherever you stage changes in git—applicable across all repositories and team sizes.