allcll-commit

Create Korean conventional commit messages and staged commit splits for allcll-backend changes.

26|1|Updated Jan 8, 2025
One-click install
npx skills add https://github.com/allcll/allcll-backend --skill allcll-commit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: allcll-commit
Source: https://github.com/allcll/allcll-backend/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/allcll/allcll-backend --skill allcll-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

이 Skill은 allcll-backend에서 커밋 생성, 커밋 메시지 작성, staging/commit 분할을 할 때 일관된 규칙을 적용해 커밋 품질을 높여줍니다.

Core Features & Use Cases

  • 커밋 메시지 작성: 최근 AI식 영어 문구를 피하고, 한국어 conventional commit 형식에 맞는 메시지를 만듭니다.
  • 작업 단위 분할: 작은 변경을 기준으로 staging과 commit을 분리해 깔끔한 히스토리를 유지합니다.
  • 프로젝트 맥락 반영: 2026년 초 main 브랜치 히스토리 스타일을 기준으로 allcll-backend에 맞는 커밋 관행을 따릅니다.

Quick Start

allcll-backend의 변경 내용을 바탕으로 한국어 conventional commit 메시지와 적절한 staging 분할안을 제안해줘.

Frequently Asked Questions about allcll-commit

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

FAQPage Schema
How do I write Korean conventional commit messages for git?▼

Korean conventional commit messages follow structured formats with type prefixes like feat or fix, avoiding AI-style English phrasing. This Skill generates compliant Korean commit messages and proposes staging splits based on allcll-backend project rules.

What is the best way to split git staging and commits by task unit?▼

Splitting git staging and commits by task unit involves separating small changes into individual commits to maintain a clean history. This Skill analyzes your changes and proposes appropriate staging divisions aligned with conventional commit standards.

Does this Korean commit message tool work with any git repository?▼

This Korean commit message tool is specifically tailored for the allcll-backend repository, applying project-specific commit style rules and main branch workflow conventions established in early 2026. It may not suit arbitrary repositories.

Why should I avoid AI-style English phrasing in Korean commit messages?▼

Avoiding AI-style English phrasing in Korean commit messages ensures natural language flow and adherence to project-specific style rules. This Skill drafts messages that reflect authentic Korean conventional commit practices without modern AI translations.

How do I organize small task-based git history in a main branch workflow?▼

Organizing small task-based git history in a main branch workflow requires splitting staging and commits by logical change units. This Skill provides staging division proposals and Korean conventional commit messages for clean history maintenance.