git-commit

Generate git commit messages conforming to the Conventional Commits v1.0.0 specification.

1|Updated Oct 21, 2025
One-click install
npx skills add https://github.com/wredzio/core2 --skill git-commit-wredzio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/wredzio/core2/tree/main/.claude/skills/git-commit
Command: npx skills add https://github.com/wredzio/core2 --skill git-commit-wredzio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams enforce consistent, machine-readable commit messages that improve changelogs and semantic versioning.

Core Features & Use Cases

  • Conventional Commits compliance: Ensure every commit follows v1.0.0 typing rules (feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert).
  • Changelog-ready messages: Messages are structured to automatically generate release notes and semantic versions.
  • Use Case: When preparing a release, provide a concise subject and optional scope; the skill outputs a compliant commit message ready to copy into the terminal.

Quick Start

Create a new feature commit by telling the skill: "feat(auth): add OAuth login support"

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate conventional commits messages automatically?

To generate conventional commits messages automatically, provide a concise subject and optional scope. The skill outputs a structured commit message with validated types, scopes, and breaking change indicators compliant with the v1.0.0 specification.

How do I format breaking changes in conventional commits?

To format breaking changes in conventional commits, the skill applies the v1.0.0 specification rules for the breaking change indicator. It structures the header and validates the type to ensure the message correctly flags breaking changes for semantic versioning.

What commit types are valid for conventional commits?

Valid commit types for conventional commits include feat, fix, docs, style, refactor, perf, test, build, ci, chore, and revert. The skill enforces type validation to ensure your commit messages strictly adhere to these standardized categories.

Does this tool generate changelog-ready git commit messages?

Yes, this tool generates changelog-ready git commit messages. By enforcing standardized and machine-readable entries with proper types and scopes, the outputted messages are structured to automatically generate release notes and determine semantic versions.

How do I structure a git commit message for semantic versioning?

To structure a git commit message for semantic versioning, use the conventional commits format with a validated type, optional scope, and breaking change indicator. This ensures the commit is machine-readable for automated changelog and release generation.

Can I use conventional commits for code review automation?

Yes, you can use conventional commits for code review automation. By generating strictly standardized and machine-readable commit messages, the skill ensures consistent typing rules that integrate smoothly with automated code review and release processes.