skills.rest
SJLee-0525
SJLee-0525COMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-commit-convention

Generates Git commit messages following a typed Korean-language convention.

Updated Jul 1, 2026
Search Tags:#git#workflow#version control#commit message#korean#git diff#convention
One-click install
npx skills add https://github.com/SJLee-0525/aperture --skill git-commit-convention-sjlee-0525
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-convention
Source: https://github.com/SJLee-0525/aperture/tree/main/.claude/skills/git-commit-convention
Command: npx skills add https://github.com/SJLee-0525/aperture --skill git-commit-convention-sjlee-0525

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-structured Git commit messages is easy to neglect, leading to unreadable project history. This Skill enforces a defined commit convention so every commit follows the same typed format. ## Core Features & Use Cases - Typed Commit Format: Generates messages in the [TYPE] 한글 제목 format using 11 defined types (FEAT, FIX, DOCS, REFACTOR, STYLE, TEST, CHORE, DESIGN, RENAME, REMOVE, !HOTFIX). - Staged Changes Analysis: Runs git diff --staged to inspect changes and select the appropriate commit type automatically. - Validation Checklist: Verifies the type is valid, the Korean title is under 50 characters, and each commit contains a single logical change. - Use Case: After staging a bug fix for a mobile layout issue, ask for a commit message and receive [FIX] 모바일에서 hero 이미지 잘림 수정 with an optional explanatory body. ## Quick Start Review my staged changes and write a commit message following the commit convention.

Frequently Asked Questions about git-commit-convention

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

FAQPage Schema
How do I write a conventional Git commit message?▼

Use the format [TYPE] title, where TYPE is an uppercase English keyword like FEAT, FIX, or REFACTOR, followed by a concise title under 50 characters. Add an optional body separated by a blank line explaining what changed and why.

How to choose the right commit type for staged changes?▼

Run git diff --staged to inspect the changes, then map them to a type: FEAT for new features, FIX for bugs, DOCS for documentation, REFACTOR for restructuring, CHORE for tooling, and DESIGN for CSS or UI changes.

Can commit messages be written in Korean?▼

Yes, this convention requires titles written in Korean without a trailing period, while the commit type stays in uppercase English. The title should remain under 50 characters based on English character count.

What commit types are supported in this convention?▼

Eleven types are defined: FEAT, FIX, DOCS, REFACTOR, STYLE, TEST, CHORE, DESIGN, RENAME, REMOVE, and !HOTFIX for urgent critical bug fixes. Each maps to a specific category of change.

When should a commit include a body section?▼

Include a body when the change needs explanation of what was modified and why, separated from the title by a blank line. Trivial changes can omit the body entirely.

Related Skills

Explore More Software Engineering Skills→
yamato0811yamato0811

git-commit-executor

Analyze git changes and create logical Conventional Commits.

Community
Intermediate
santychuycomsantychuycom

ship

Analyze diffs, create atomic conventional commits, push, and open pull requests.

Official
Advanced
cropsggcropsgg
15

pre-commit-setup

Install Husky and configure lint-staged for staged-file checks.

Community
Intermediate
whitebearditwhitebeardit
12

conventional-commits

Validate commit messages and PR titles against Conventional Commits rules.

Official
Intermediate