commit

Create Conventional Commits messages with type prefixes and descriptive bodies.

Updated Jul 18, 2022

Search Tags:#git #commit #best-practices #version-control #conventional-commits #changeset

Ready to run

npx skills add https://github.com/milosptr/pos-system --skill commit-milosptr

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating meaningful, consistently formatted commit messages that accurately describe changes to the codebase.

Core Features & Use Cases

Conventional Commit style: Enforces type prefixes like feat, fix, refactor, docs, and chore to standardize history.
Message structure: Encourages a concise subject line and a detailed body with optional Co-Authored-By lines for attribution.
Workflow integration: Suitable for code reviews, release notes generation, and audit trails across teams.

Quick Start

Stage relevant changes and create a well-formatted commit message using the Conventional Commits style.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I write conventional commit messages for my staged git changes?▼

To write conventional commit messages, apply standardized type prefixes like feat, fix, or refactor to your staged git changes, followed by a concise subject line and a detailed body describing the codebase modifications.

What is the correct structure for a conventional commit message?▼

A conventional commit message requires a type prefix such as feat or chore, a concise subject line, an optional detailed body explaining the changes, and optional Co-Authored-By lines for proper attribution.

Can I use conventional commits to generate release notes and audit trails?▼

Yes, conventional commits standardize your version-control history with type prefixes, making the commit log suitable for automated release notes generation, code reviews, and maintaining clear audit trails across teams.

When do I need to use specific type prefixes in version control?▼

You need type prefixes in version control whenever you want a clean git history that clearly categorizes changes into features, fixes, refactors, or chores for better codebase maintenance and code review workflows.

What's the best way to format a git commit body for code reviews?▼

The best way to format a git commit body for code reviews is to provide a detailed explanation of the changeset immediately after a concise subject line, ensuring reviewers understand the context and purpose of the modification.