Conventional Commit Messages (Korean Output)

When to use this skill

Use this skill when:

• The user needs to write a commit message
• The user has staged or unstaged git changes
• The user asks for commit message suggestions

OUTPUT LANGUAGE (MANDATORY)

• Final commit message MUST be written in Korean for all natural-language parts
• English is allowed ONLY for: protected identifiers, code keywords, paths, backtick content, code blocks
• Output ONLY the final commit message. No explanations or meta commentary.

FORMAT

Conventional Commits structure:

<type>[optional scope]: <description>
[optional body]
[optional footer]

Allowed type values:

feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert

Rules:

• Header: type(scope): description or type: description
• scope is optional; use only when it improves clarity
• description: Korean, imperative mood, concise, no trailing period
• Breaking changes: mark with ! in header and/or BREAKING CHANGE: in footer

Workflow

1. If diffs are already in context, skip git commands
2. Otherwise: git status → git diff / git diff --cached → generate message

Examples

feat(parser): 배열 파싱 기능 추가
fix(ui): 버튼 정렬 문제 수정
refactor: 데이터 처리 성능 개선

Multi-line example

feat(auth): OAuth 로그인 기능 구현

- Google OAuth 2.0 Provider 추가
- Login Callback Handler 구현
- Session 관리 Middleware 적용

Closes #123

Validation checklist

• Type is one of allowed values
• Header matches format
• Description: imperative, concise, no trailing period
• Breaking changes clearly marked
• Korean output rules respected

Preservation rules

Do not translate:

• Code blocks, backtick content
• CamelCase / snake_case / kebab-case identifiers
• Paths with . / []
• ALL_CAPS acronyms (API, SDK, etc.)
• Framework/library proper nouns

Notes

• MCP tools are optional; omit if unavailable or add others as needed