git-commit

Enforce Korean commit messages with type prefixes and optional multi-line bodies.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/GreenFirst-kr/green_first_be --skill git-commit-greenfirst-kr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/GreenFirst-kr/green_first_be/tree/main/.claude/skills/git/commit
Command: npx skills add https://github.com/GreenFirst-kr/green_first_be --skill git-commit-greenfirst-kr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces Korean commit messages with strict rules and consistent structure to improve traceability and readability of project history.

Core Features & Use Cases

  • Korean language commits: All messages must be in Korean.
  • Type prefixes: Enforces feat/fix/refactor/test/chore prefixes.
  • Detailed body support: Allows an optional detailed multi-line body for complex changes.
  • Use Case: When contributing to a project, ensure every commit follows the standardized format.

Quick Start

Ask to create a commit message and follow the conventions described.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I enforce Korean commit message conventions automatically?

Korean commit conventions require messages written in Korean with specific type prefixes like feat, fix, refactor, test, or chore. This format standardizes project history, improving traceability and readability for all repository contributions.

What type prefixes are required for Korean git commits?

Required type prefixes for Korean git commits include feat, fix, refactor, test, and chore. Enforcing these prefixes structures the version control history, making it easier to categorize and track project changes accurately.

Can I include a detailed multi-line body in my Korean commit message?

Yes, you can include an optional detailed multi-line body in your Korean commit message. This feature supports complex change descriptions while maintaining the required Korean language and type prefix conventions.

Does this Korean commit convention workflow handle git rebase or pull request actions?

No, this Korean commit convention workflow does not handle git rebase or pull request actions. It specifically focuses on new commits, commit reviews, and adherence checks without managing basic git setup or repository branching operations.

When do I need to use standardized Korean commit conventions in version control?

You need standardized Korean commit conventions when contributing to a project repository requiring strict language and prefix discipline. This ensures traceability and readability across the version control history for all team members.