skills.rest
xobotyi
xobotyiCOMMUNITY
Explore all skills by this author →
𝕏@xobotyiGitHub

commit-message

Enforce Git commit message structure, formatting, scoping, body content, and trailers.

19|Updated Jan 30, 2026
Search Tags:#git#developer tools#code review#version control#commit#conventional commits
One-click install
npx skills add https://github.com/xobotyi/cc-foundry --skill commit-message-xobotyi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-message
Source: https://github.com/xobotyi/cc-foundry/tree/main/plugins/git-commit/skills/commit-message
Command: npx skills add https://github.com/xobotyi/cc-foundry --skill commit-message-xobotyi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes and improves the quality of Git commit messages, ensuring clarity, consistency, and adherence to best practices for better code history and collaboration.

Core Features & Use Cases

  • Structured Commit Format: Enforces a clear [scope] subject, body, and trailers structure.
  • Factual & Imperative Subjects: Guides users to write concise, action-oriented subject lines.
  • Contextual Body: Prompts for essential explanations of why changes were made and how to verify them.
  • Breaking Change Declaration: Ensures backward-incompatible changes are clearly marked.
  • Trailer Standardization: Facilitates the use of metadata like Task:, Fixes:, Refs:, etc.
  • Use Case: Before committing a bug fix, use this Skill to ensure your commit message clearly states the problem, the cause, the fix, and links to the relevant issue tracker.

Quick Start

Use the commit-message skill to help write a commit message for a change that fixes a bug in the user authentication module.

Frequently Asked Questions about commit-message

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

FAQPage Schema
How do I write a conventional Git commit message?▼

A conventional Git commit message requires a structured format with a clear scope and imperative subject, a contextual body explaining why changes were made, and standardized trailers for metadata. This enforces factual communication for effective code history.

What should be included in a Git commit message body?▼

A Git commit message body should include essential explanations of why changes were made and how to verify them. This provides the context necessary for effective code review and collaboration, ensuring the reasoning behind modifications is documented.

How do I declare breaking changes in version control commits?▼

To declare breaking changes in version control commits, clearly mark backward-incompatible changes within the structured commit message. This standardization ensures developers are immediately aware of modifications that impact existing functionality.

What is the best way to format commit trailers for issue tracking?▼

The best way to format commit trailers for issue tracking is to standardize metadata using tags like Task:, Fixes:, and Refs:. This facilitates linking commits to relevant issue trackers and provides clear context for code review.

Does standardizing commit messages improve code review?▼

Standardizing commit messages improves code review by enforcing a factual, imperative, and context-rich structure. Clear subjects and contextual bodies help reviewers quickly understand the problem, cause, and fix without guessing the intent.

Related Skills

Explore More Software Engineering Skills→
tomlupotomlupo

generating-commit-messages

Generate structured Git commit messages from staged changes.

Community
Basic
mattg101mattg101
1

gcp-copy

Stage all changes, commit with a message, and push to a remote Git repository.

Community
Basic
Quill-AgentQuill-Agent
3

requesting-code-review

Automate pre-commit code review with security scans and quality checks.

Community
Advanced
dennisonbertramdennisonbertram
1

changelog-gen

Generate release notes from Git history using Conventional Commits and git-cliff.

Community
Advanced