conventional-commit

Generate Conventional Commits messages with English types and Korean descriptions.

Updated Mar 10, 2026
Ready to run
npx skills add https://github.com/Palbahngmiyine/harness --skill conventional-commit-palbahngmiyine
πŸ’¬ Prompt for ChatGPT / Claude Chatβ–Ό
Please help me install this Agent Skill.
Skill: conventional-commit
Source: https://github.com/Palbahngmiyine/harness/tree/main/skills/conventional-commit
Command: npx skills add https://github.com/Palbahngmiyine/harness --skill conventional-commit-palbahngmiyine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional commit messages provide clear, machine-readable release notes and improve traceability across a codebase. This skill generates such messages automatically according to the Conventional Commits specification.

Core Features & Use Cases

  • Generate messages with type, optional scope, and a structured description
  • Enforce language guidelines: English types, English scope, Korean description/body, and Korean footer keywords
  • Use cases include feature additions, bug fixes, docs updates, and release-note preparation

Quick Start

λ³€κ²½ λ‚΄μš©μ„ κ°„λ‹¨ν•˜κ²Œ μž‘μ„±ν•˜λ©΄ 이 μŠ€ν‚¬μ΄ Conventional Commits ν˜•μ‹μ˜ 컀밋 λ©”μ‹œμ§€λ₯Ό μžλ™μœΌλ‘œ μƒμ„±ν•©λ‹ˆλ‹€.

Frequently Asked Questions about conventional-commit

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

FAQPage Schema
How do I generate conventional commit messages with Korean descriptions?β–Ό

To generate conventional commit messages with Korean descriptions, you provide your changes and the skill outputs standardized messages using English types like feat or fix, optional scope, and Korean description and body text.

What is the conventional commits format for structuring git commit messages?β–Ό

The conventional commits format structures git commit messages using a specific type, an optional scope, a description, a body, and a footer to produce clear, machine-readable release notes and improve traceability.

Can I use English types and scopes with Korean body text in a git commit?β–Ό

Yes, you can use English types and scopes with Korean body text in a git commit. The skill enforces language guidelines requiring English for types and scopes, Korean for descriptions and bodies, and bilingual footer keywords.

How do I prepare release notes from conventional commit messages?β–Ό

You prepare release notes from conventional commit messages by applying the specification's structured format, which uses bilingual footer keywords to produce clear, machine-readable outputs suitable for release-note preparation.

What is the best way to automate standardized git commit message generation?β–Ό

The best way to automate standardized git commit message generation is to input your changes and let the skill automatically format them into the conventional commits specification with correct types, scopes, and descriptions.

Do I need any dependencies to create conventional commits?β–Ό

No, you do not need any dependencies to create conventional commits with this skill, as it operates independently without requiring external components or modules to generate the standardized messages.