committing

Generate conventional commit messages with type, scope, and description.

23|2|Updated Jun 9, 2025
One-click install
npx skills add https://github.com/kaptinlin/gozod --skill committing-kaptinlin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: committing
Source: https://github.com/kaptinlin/gozod/tree/main/.agents/skills/committing
Command: npx skills add https://github.com/kaptinlin/gozod --skill committing-kaptinlin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates conventional commits following project commit conventions. Use when committing code changes, creating commit messages, or when the user asks to commit staged changes.

Core Features & Use Cases

  • Commit Message Format: enforce "<type>(<scope>): <description>" style with optional body.
  • Pre-commit Checks: ensure messages comply with rules and prevent improper commits.
  • Workflow Guidance: provide a structured process for staging, reviewing, and finalizing commits.

Quick Start

Follow the commit guide to craft compliant messages for each change.

Frequently Asked Questions about committing

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

FAQPage Schema
How do I write conventional commit messages for git?

Conventional commits use a structured format like "<type>(<scope>): <description>" to standardize git workflow messaging. This format ensures consistent version-control history across software projects by enforcing specific commit type rules.

What is the correct format for a breaking change in a conventional commit?

A breaking change in a conventional commit is indicated using a specific breaking change indicator within the message structure. The commit format still requires a type and imperative description, while Co-Authored-By trailers are explicitly excluded.

How do I automate commit lint checks before finalizing a git commit?

Automate commit lint checks by applying pre-commit rules that verify the message complies with conventional commit standards. This prevents improper commits and enforces a structured staging, reviewing, and finalizing workflow.

Does this conventional commit workflow require a scope in the commit message?

Conventional commit workflow requires a commit type and an imperative description, but the scope is optional. You can include a scope in parentheses to specify the context of the change if needed.

Are Co-Authored-By trailers included in these conventional commit messages?

Co-Authored-By trailers are explicitly excluded from these conventional commit messages. The workflow focuses strictly on the type, optional scope, description, and breaking change indicators to maintain a clean project history.