commit-message-generator

Generate structured Korean commit messages with headers and body sections.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Mockly-Company/mockly-mobile --skill commit-message-generator-mockly-company
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-message-generator
Source: https://github.com/Mockly-Company/mockly-mobile/tree/main/.claude/skills/commit-message-generator
Command: npx skills add https://github.com/Mockly-Company/mockly-mobile --skill commit-message-generator-mockly-company

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill formats commit messages per the project's conventions, generating Korean commit messages with header, body and optional sections.

Core Features & Use Cases

  • Header/body formatting: Produces appropriate format.
  • Co-authorship note: Appends generated footer with co-author tag.

Quick Start

Run the CLI to generate a commit message for the current staged changes.

Frequently Asked Questions about commit-message-generator

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

FAQPage Schema
How do I generate consistent Korean commit messages for my Git project?

Korean commit messages are generated automatically by applying your project's conventions. The Skill formats messages with a Korean header (max 50 characters), commit type (feat, fix, docs, style, refactor, test, chore, perf, ci, build, revert), and a structured body with sections for explanation, additional content, changes, and related issues.

Can I automate commit message formatting to match my team's Git conventions?

Yes. This Skill enforces your project's defined commit conventions automatically, ensuring all messages follow the same header and body structure. It appends a co-author footer and applies formatting rules consistently across your team.

What commit types and message structure does the automation support?

The Skill supports all standard commit types: feat, fix, docs, style, refactor, test, chore, perf, ci, build, and revert. Messages include a formatted header, body with 설명, 추가 내용, 변경 내용, and 관련 이슈 sections, plus optional co-author tags.

How do I trigger commit message generation from the command line?

Run the CLI to generate a commit message for your currently staged changes. The Skill activates when you request commits or use Korean phrases like '커밋 만들어줘' or 'git commit 해줘', then formats the message according to your project's conventions.

Does this work if my project doesn't have predefined commit conventions yet?

The Skill applies your project's defined conventions. If conventions are not yet established, you'll need to define your project's header and body structure, allowed commit types, and character limits before the automation can enforce formatting consistently.