git-commit

Generate Korean Conventional Commits 1.0.0 messages with type and scope guidance.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/aroido/vibesmith --skill git-commit-aroido
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/aroido/vibesmith/tree/main/.cursor/skills/git-commit
Command: npx skills add https://github.com/aroido/vibesmith --skill git-commit-aroido

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers generate Git commit messages that adhere to the Conventional Commits 1.0.0 specification, ensuring consistency and clarity in version control history, with a specific focus on Korean language usage.

Core Features & Use Cases

  • Conventional Commits Compliance: Automatically formats commit messages according to the standard <type>[optional scope]: <description>\n\n[optional body]\n\n[optional footer(s)].
  • Korean Language Support: Mandates that descriptions, bodies, and footers are written in Korean.
  • Comprehensive Type Guidance: Details various commit types (feat, fix, build, chore, etc.) and their implications for Semantic Versioning.
  • Breaking Change Handling: Provides clear methods for indicating breaking changes using ! or the BREAKING CHANGE footer.
  • Workflow Guidance: Offers a step-by-step process for analyzing changes, selecting types, and writing effective commit messages.
  • Anti-pattern Examples: Illustrates common mistakes to avoid in commit message writing.
  • Tool Recommendations: Suggests tools like Commitlint, Commitizen, and Husky for enhanced commit workflows.

Quick Start

Use the git-commit skill to generate a commit message for a new feature that adds user authentication.

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 commits in Korean?β–Ό

To format conventional commit messages for semantic versioning, follow the `<type>[optional scope]: <description>` standard, choosing appropriate types like `feat` or `fix` to indicate version bumps. This Skill provides comprehensive type guidance and anti-pattern examples to ensure correct versioning implications.

How do I indicate breaking changes in a conventional commit?β–Ό

Indicate breaking changes in a conventional commit by appending a `!` after the type and scope, or by adding a `BREAKING CHANGE` footer. This Skill provides clear methods and examples for handling breaking changes according to the 1.0.0 specification.

What is the correct conventional commit format for a new feature?β–Ό

Tools like Commitlint, Commitizen, and Husky enhance conventional commit workflows by enforcing message standards and guiding interactive submissions. This Skill recommends these specific tools to improve your version control history consistency.

What are common anti-patterns when writing Git commit messages?β–Ό

Common anti-patterns when writing Git commit messages include using vague descriptions, omitting appropriate commit types, and failing to structure bodies clearly. This Skill illustrates these common mistakes to help you avoid them and maintain a clean version control history.