메뉴
Use when user asks commit/stage/unstage/split commits/draft commit msg. Inspect full worktree by default, group changes into behavior commits, protect secrets/accidental files, keep user-excluded scope untouched.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | git-commit |
| description | Use when user asks commit/stage/unstage/split commits/draft commit msg. Inspect full worktree by default, group changes into behavior commits, protect secrets/accidental files, keep user-excluded scope untouched. |
| compatibility | Requires git CLI + shell in repo worktree. |
| allowed-tools | Bash(git:*) Bash(cat:*) Bash(sed:*) Bash(grep:*) Bash(file:*) Bash(mktemp:*) Bash(wc:*) Read |
| metadata | {"version":"2.0.0"} |
Make repo-fit commits from current worktree.
Use only for commit/stage/unstage/split/msg draft. Not generic Git/branch/rebase/squash/publish unless user asks.
Defaults:
Stop if: not Git repo, conflicts/merge/rebase/cherry-pick not requested, detached HEAD not accepted, in-scope secret/local config, out-of-scope staged changes cannot separate, hooks/validation fail.
Risk files: .env, .npmrc, .pypirc, cloud creds, private keys, tokens, passwords, IDE files, caches, large binaries, ignored -f.
From root:
git rev-parse --show-toplevel
git status --short --branch
git diff --stat
git diff --cached --stat
git diff
git diff --cached
git ls-files --others --exclude-standard
git diff --name-only --diff-filter=U
git log --format='%h %s' -n 20
git log --format='%B%x00' -n 5
git config --show-origin --get-all commit.template
Template exists? Read file. Non-comment text = msg constraint.
Untracked/large/binary before stage:
file -- <path>
wc -c -- <path>
sed -n '1,200p' -- <path>
Narrowed scope:
git commit.Group by behavior. Keep code/tests/fixtures/generated/docs/config together when one logical change. Split independent concerns even same file. Prereqs first. Read diffs, not names/stats.
For each group:
git add -p or git apply --cached).git add -f ignored file unless user named it.git diff --cached --stat
git diff --cached
git diff --cached --check
Unrelated hunks staged? Fix index first.
Message: follow history/template. Prefer recent dominant style; type(scope): verb phrase if fits. Imperative subject. No file list/trailing period. Body only for why/migration/constraints/validation/side effects. Commit via temp file + git commit -F <file>.
Run cheap relevant checks when obvious. Never claim pass unless run + succeeded. No --no-verify unless asked; final says bypassed.
Loop until in-scope committed or blocked. After each commit:
git status --short
git diff --stat
git diff --cached --stat
git log --oneline -n 5
Report commits hash+subject, grouping, validation/hooks, in-scope left+why, out-of-scope untouched. No commit? exact reason + status.
Unified scoped code review + parent-owned fix loop. Use for /review-loop, review until clean, code review with fixes, or modes: web, server, database, node, planning.
Orchestrate implementation work from intake to closeout. Use when the user asks to run a task through a consistent work flow, plan first, turn a plan into Taskwarrior tasks, execute task-by-task, verify, review, and optionally prepare commits. Trigger phrases include workstream, 작업흐름, 작업 흐름, 기획부터 태스크화, 계획 세우고 구현, and 태스크화해서 구현.
Convert implementation plans, Markdown checklists, and work items into a Taskwarrior task queue. Use when the user asks to queue, taskify, 태스크화, 작업 큐, 작업 등록, plan to tasks, checklist to tasks, or when workstream needs a Taskwarrior draft from plan Work Items. Shows a concise user-language summary before mutation and delegates command safety to the taskwarrior skill.
Close out implementation work by checking plan completion, Taskwarrior queue status, validation results, review findings, git status, residual risk, and commit readiness. Use when the user asks to close, finish, wrap up, 마감, 완료 정리, 종료 정리, or when workstream reaches its closeout phase. Does not commit by itself; delegates commits to git-commit only when requested.
Map a repository or working directory before implementation. Use when the user asks to survey, scan, inspect, orient, 구조 파악, 훑어보기, 작업 전 파악, or when workstream needs a pre-implementation map of project structure, package manager, commands, tests, local apps, ownership boundaries, and risk areas. Produces concise findings and recommended next checks without making code changes.
Choose and run validation for code, docs, config, UI, API, database, refactor, and bugfix work. Use when the user asks to verify, validate, test, confirm, check, 검증, 확인, 테스트, or when workstream needs a consistent validation matrix before marking tasks done. Produces focused checks, pass/fail criteria, and exact skipped or blocked validation gaps.