What problem does it solve?
Commit titles often become vague, too long, or ignore project conventions, while branch names drift into inconsistent patterns and workflow artifacts sneak into commits; git-master stops those issues by enforcing Korean noun-form messages, 50-character limits, and disciplined branch naming before changes land. It codifies the Iron Law, workflow file exclusion rules, and atomic commit planning so agents can rely on consistent guidance for every commit scenario.
Core Features & Use Cases
- Iron Law enforcement: Guarantees that each commit represents a single logical change with a Korean title under 50 characters and recommends imperative mood endings so history stays readable.
- Atomic change planning: Triggers multi-commit planning when more than three files are touched, explains how to justify grouped files, and keeps tests paired with their implementations.
- Workflow artifact safeguard: Reminds agents to unstage
plan.md, research.md, and docs/specs/ before committing to prevent leaking research or spec inputs.
- Use Case: When preparing a checkpoint for an oh-my-toong project that mixes code, tests, and docs, rely on git-master to audit the staged diff, decide whether to split commits, and keep the branch name aligned with conventions.
Quick Start
Ask git-master to review your staged changes and return a Korean commit title under 50 characters plus branch naming guidance before you commit.
