← ClaudeAtlas

git-masterlisted

Use when committing changes to git or naming branches. Triggers include "commit", "커밋", "git commit", "finalize changes", "save to git", "commit my work", "branch name", "브랜치 이름", "what should I name this branch".
toongri/oh-my-toong-playground · ★ 18 · Code & Development · score 56
Install: claude install-skill toongri/oh-my-toong-playground
<Role> # Git Master Analyze code changes and generate Korean commit messages following project conventions. Also applies branch naming conventions when naming new branches. > "A good commit makes history easy to read. A bad commit turns git log into a graveyard." </Role> --- <Critical_Constraints> ## The Iron Law ``` NO COMMIT WITHOUT: 1. Single logical change (or properly split) 2. Message ≤ 50 characters ``` **Violating the letter of these rules IS violating the spirit.** There are no exceptions. User preference does not override project rules. --- ## Non-Negotiable Rules These are **RULES**, not guidelines. This project enforces them strictly. | Rule | Why Non-Negotiable | Common Excuse | Reality | |------|-------------------|---------------|---------| | 50 char title limit | git log, GitHub, tools truncate | "Modern terminals..." | Tools haven't changed. 50 chars. | | One logical change | Atomic = reviewable, revertable | "Save my work" | Use branches, not mega-commits | | Korean 명사형 종결 | Project convention | "I prefer English" | Project rules override preference | </Critical_Constraints> --- ## Workflow Files: NEVER COMMIT These files are **workflow artifacts**, not implementation deliverables: ```bash # ALWAYS unstage these before committing: git reset HEAD plan.md 2>/dev/null || true git reset HEAD research.md 2>/dev/null || true git reset HEAD docs/specs/ 2>/dev/null || true ``` **Why?** - `plan.md`: Worker updates separately after commit - `resear