commit-message

Name: commit-message
Availability: InStock
Author: LMMs-Lab

Enforce Conventional Commits formatting with type: subject and body guidelines.

1.2k|78|Updated Sep 16, 2025

Search Tags:#git #workflow #documentation #commit #style #release-management #conventional-commits

Ready to run

npx skills add https://github.com/EvolvingLMMs-Lab/LLaVA-OneVision-2 --skill commit-message-evolvinglmms-lab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/EvolvingLMMs-Lab/LLaVA-OneVision-2/tree/main/.opencode/skills/commit-message
Command: npx skills add https://github.com/EvolvingLMMs-Lab/LLaVA-OneVision-2 --skill commit-message-evolvinglmms-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Commit messages in collaborative projects are often inconsistent, making it hard to generate changelogs, track changes, and understand history. This skill provides a clear, repeatable convention that improves traceability and release management.

Core Features & Use Cases

Enforces the Conventional Commits style across all commits to standardize messaging.
Documents the allowed types (feat, fix, docs, test, chore, refactor, etc.) and the expected subject/body structure.
Use cases include helping maintain changelog pages, improving code review clarity, and enabling automated release notes.

Quick Start

Begin every commit with a type and subject using the format type: subject, followed by an optional body if needed.

Frequently Asked Questions about commit-message

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

FAQPage Schema

How do I enforce conventional commit messages in a git workflow?▼

To enforce conventional commit messages in a git workflow, apply formatting rules that require a type: subject structure, ensuring subject lines meet length constraints and body guidelines for traceability.

What is the conventional commits format for type and subject lines?▼

The conventional commits format structures messages as type: subject, using types like feat, fix, docs, or chore, followed by an optional body to document changes and improve code review clarity.

How do I standardize commit messages to automate release notes and changelogs?▼

Standardize commit messages using conventional commits to automate release notes and changelogs, applying consistent type prefixes and subject constraints to parse project history accurately.

Can I use conventional commits for local commits in collaborative software projects?▼

Yes, you can use conventional commits for local commits in collaborative software projects to standardize messaging, improve changelog quality, and enable consistent release management workflows.

What are the limitations of enforcing conventional commit message style?▼

Limitations of enforcing conventional commit message style include the strict adherence required to length constraints and type prefixes, which may disrupt existing project history if not applied consistently.

Does commit-message work with release management and changelog generation?▼

Commit-message works directly with release management and changelog generation by enforcing conventional commit formatting, ensuring consistent documentation across collaborative software projects.