commit

Generate Conventional Commit messages from staged changes with Korean bodies.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/MayMustAI/ai-dev-playbook --skill commit-maymustai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/MayMustAI/ai-dev-playbook/tree/main/plugins/maymust/skills/commit
Command: npx skills add https://github.com/MayMustAI/ai-dev-playbook --skill commit-maymustai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MayMust 팀 컨벤션으로 git 커밋을 생성. 스테이지된 변경을 분석해 Conventional Commits 형식(한글 본문)으로 메시지를 제안·실행. "커밋 메시지 뽑아줘", "이거 커밋해줘", "/commit" 호출 시 사용.

Core Features & Use Cases

  • Meaningful 모드: 핵심 변경 단위에 제목 + 본문으로 커밋 메시지를 작성하고 리뷰 대상으로 남긴다.
  • wip 모드: 진행 중인 작업의 제목만 남겨 임시 저장용 커밋을 생성한다.
  • 규칙 준수: 타입(type)과 스코프(scope), 본문 구성(한글 본문 + 용어)까지 팀 컨벤션에 맞춘 메시지를 자동으로 생성한다.

Quick Start

Use /commit to analyze staged changes and commit them using the team's Conventional Commits format.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages automatically from staged changes?

To generate conventional commit messages automatically, you can use a workflow that analyzes your staged git changes and proposes a structured message. This ensures your commits enforce type, scope, and description formats aligned with your team conventions.

What is the best way to write meaningful git commit messages for code review?

The best way to write meaningful git commit messages for code review is to use a meaningful mode that creates a title and body for core changes. This leaves a clear, descriptive record of what was changed and why it warrants review.

Can I create a temporary work-in-progress commit without writing a full message?

Yes, you can create a temporary work-in-progress commit by using a wip mode. This mode generates a commit with only a title, allowing you to quickly save ongoing work across dev and main branches without a full message body.

Does this conventional commits workflow support Korean message bodies?

Yes, this conventional commits workflow supports Korean message bodies. It automatically generates the body text in Korean while enforcing your specific type, scope, and description structure for your daily development workflow.

How do I enforce team conventions for git commits across daily development workflows?

To enforce team conventions for git commits across daily development workflows, apply an automated process that structures messages with specific types and scopes. This ensures every commit on dev and main branches adheres to your team's formatting rules.