git-commit

Create git commits following the Conventional Commits format with type, scope, and subject.

Updated Mar 16, 2026

Search Tags:#git #workflow #versioning #scope #commit-message #conventional-commits #heredoc

Ready to run

npx skills add https://github.com/woernfl/ai-lab --skill git-commit-woernfl

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/woernfl/ai-lab/tree/main/skills/git-commit
Command: npx skills add https://github.com/woernfl/ai-lab --skill git-commit-woernfl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creates git commits that follow the Conventional Commits format, ensuring consistent messaging across the codebase and simplifying changelog generation.

Core Features & Use Cases

Generate commits with type, scope, and subject to meet CC rules.
Enforce scope in parentheses and use present-tense imperative verbs.
Support multi-line commit messages via heredoc for complex changes.
Stage changes and commit during daily development workflow.

Quick Start

Stage changes and commit with a type/scope/subject message.

Frequently Asked Questions about git-commit

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

FAQPage Schema

How do I write conventional commit messages with a scope in git?▼

To create conventional commits, you stage changes and commit using a type, scope, and subject structure. This ensures consistent messaging across your codebase and simplifies changelog generation.

What is the conventional commits format for git commit messages?▼

The conventional commits format structures messages with a type, scope in parentheses, and a subject. It requires present-tense imperative verbs and validates subject length to maintain consistent versioning.

Can I create multi-line git commit messages for complex changes?▼

Yes, multi-line git commit messages are supported via heredoc syntax. This allows you to detail complex changes while maintaining the conventional commits type, scope, and subject structure.

How do I stage changes and commit with conventional commits format?▼

You stage changes and commit with a type, scope, and subject message to meet conventional commits rules. This enforces scope in parentheses and present-tense imperative verbs for daily development.

Why enforce a scope in parentheses for conventional commit messages?▼

Enforcing a scope in parentheses identifies the affected codebase section. Combined with present-tense imperative verbs and validated subject length, it ensures consistent messaging for simplified changelog generation.

Does this conventional commits approach work for team development workflows?▼

Yes, conventional commits are designed for software development workflows where changes are saved, staged, and committed across teams. Consistent type, scope, and subject formatting streamlines collaboration and changelog generation.