| name | git-commit |
| description | Create Git commits by splitting changes into logical units following project conventions. Handles Git Flow automatically — detects develop branch and checks out a feature branch before committing. |
| allowed-tools | Bash |
Step 0 — Branch Check (Required)
Check the current branch first:
git branch --show-current
If current branch is develop:
This project uses Git Flow. Feature branches must be created from develop and merged back into develop.
- Analyze all changes with
git status and git diff
- Infer an appropriate branch name from the changes:
- Format:
<type>/<kebab-case-description> — use the same type as the planned commit (exception: use cicd/ for ci/cd type)
- Reflect the domain scope in the name
- Examples:
add/add-student-major-filter, fix/auth-api-key-deletion, refactor/optimize-club-query
- Create and checkout the branch:
git checkout -b <type>/<inferred-name>
- Proceed with the commit flow below
If current branch is NOT develop: proceed directly to the commit flow.
Commit Message Rules
Format: type(scope): description
- Types:
add / update / fix / refactor / ci/cd / docs / test / merge
- Scope: domain name by default — for the full selection table, read
${CLAUDE_SKILL_DIR}/references/scope-guide.md; for type/scope conventions, read ${CLAUDE_SKILL_DIR}/references/commit-conventions.md
- Description: Korean, no period, avoid endings:
~한다/~된다, ~하기, ~합니다/~됩니다, ~했습니다
- Good examples:
엔티티 필드 추가, 트랜잭션 롤백 방지, 로직 개선
- Subject line only (no body)
Commit Flow
- Inspect changes:
git status, git diff
- Categorize into logical units (feature / bug fix / refactoring / etc.)
- Group files per unit
- For each group:
- Stage only relevant files with
git add
- Write a commit message following the rules above
git commit -m "message"
- Verify with
git log --oneline -n <count>
