skills.rest
matthew-h-cromer
matthew-h-cromerCOMMUNITY
Explore all skills by this author →
Website𝕏@matthew_cromer_GitHub

commit-conventions

Provide guidelines for writing structured git commit messages.

Updated Feb 21, 2026
Search Tags:#git#best practices#version control#commit#guidelines
One-click install
npx skills add https://github.com/matthew-h-cromer/workflowskill --skill commit-conventions-matthew-h-cromer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-conventions
Source: https://github.com/matthew-h-cromer/workflowskill/tree/main/.claude/skills/commit-conventions
Command: npx skills add https://github.com/matthew-h-cromer/workflowskill --skill commit-conventions-matthew-h-cromer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a clear and consistent standard for writing git commit messages, improving project clarity and traceability.

Core Features & Use Cases

  • Structured Commit Formatting: Enforces the conventional format of type, scope, subject, body, and trailers.
  • Guidance on Message Rules: Offers detailed instructions on how to craft concise, effective commit messages.
  • Use Case: When contributing to a project with multiple developers, use this Skill to ensure all commits follow the team’s agreed convention.

Quick Start

Use the commit-conventions skill to check if your current commit message adheres to the defined standards.

Frequently Asked Questions about commit-conventions

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

FAQPage Schema
What are git commit conventions and why do I need them for version control?▼

Git commit conventions are standardized guidelines for writing clear, structured commit messages that facilitate easier code review and history tracking for development teams aiming for improved collaboration.

How do I write a structured git commit message for team collaboration?▼

To write a structured git commit message, follow the conventional format of type, scope, subject, body, and trailers, keeping the message concise and effective to ensure all commits follow the team's agreed convention.

Can I use these commit message guidelines without installing external dependencies?▼

Yes, you can use these commit message guidelines without external dependencies, as the skill requires no external dependencies for operation and provides instructions on how to craft effective messages directly.

What's the best way to enforce conventional commit formatting across a development team?▼

The best way to enforce conventional commit formatting is by applying structured guidelines for type, scope, subject, body, and trailers, ensuring all team members follow the same version control practices for clear project traceability.

How do I check if my current commit message adheres to defined standards?▼

You can check if your current commit message adheres to defined standards by validating it against the structured format of type, scope, subject, body, and trailers, ensuring it meets the guidelines for clear project traceability.

Related Skills

Explore More Software Engineering Skills→
naj2rnaj2r

commit

Creates git commits with auto-generated messages and optional push.

Community
Intermediate
GlorktelligenceGlorktelligence

Git Workflow

Commit and push code changes to a remote repository using Conventional Commits.

Community
Intermediate
DGouronDGouron
41

commit

Enforce quality gates and conventional commit rules in Git workflows.

Community
Advanced
adriannoesadriannoes
46

update-changelog

Parse repository tags and commit history to generate markdown changelog entries.

Community
Basic