메뉴
Commit hygiene — before creating a commit, detect and flag unrelated changes (especially stray data fixes bundled into program commits) so they can be split into their own commits.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Picks up after /build to publish a GitHub release. Pre-flights the staged artifacts, drafts release_notes.md from commits since the last tag, tags master, then hands the gh release create upload command to the user. Stops short of running the upload — that's user-driven.
Spawn a fresh-context Opus 4.7 agent to give an independent take when Claude and the user are talking past each other on a contested logic interpretation, OR to validate behavioral self-observations from /session-recap Step 0. User-triggered or claude self-proposed at impasse.
End-of-session recap — codify learnings synchronously into their canonical homes; daily logs hold narrative continuity only.
Review dirty code and fix iteratively using Ralph loop pattern. When user say to "loop to fix dirty" or "review+fix"
Review dirty code changes using Claude Code Agent tool. When user say to "review" or "review changes" or "review dirty code"
| name | commit |
| description | Commit hygiene — before creating a commit, detect and flag unrelated changes (especially stray data fixes bundled into program commits) so they can be split into their own commits. |
| triggers | ["/commit","commit","commit changes","make a commit"] |
Keep each commit to one logical change. Mixing related data + program changes is fine. Mixing unrelated data fixes into a program commit pollutes history and breaks /release note drafting.
One clean topic → one commit. When the whole dirty tree is a single topic — including that topic's session-recap codifications (rules, memory, TODO) — make ONE commit. Don't reflexively split feature from recap; the feature+recap split is only for when they're genuinely separate topics. (2026-06-10) User: "next time when commits are clean about one topic, just make them 1 commit."
/review-dirty produced clean output.git branch --show-current. If on a feature branch and the change is unrelated to that feature, surface the mismatch before committing.memory/<today>.md covers this session's work, propose recap-first. User can say "skip recap" to waive.Skip clause: user explicitly waives ("trivial, just commit", typo fix). Applies to that commit only.
Run git status --short. The PostToolUse hook (_harness/classify_commit.py) auto-injects a classification report — read it instead of classifying manually. The report covers: file buckets, branch name, session-recap existence, data+program mix warnings.
Identify the main change from conversation context. For each file: "Does this need to change for the main ask to work?"
Red flags: unrelated data edits alongside program changes, multiple unrelated data fixes bundled, files from a parallel Claude session (not in your tool history).
Match repo commit style (git log --oneline -10). Show proposed message + any flags. Wait for user choice before committing.
For bulk additions: subject names the largest change; body enumerates the rest with counts.
git add -A / git add ..CLAUDE_COMMIT_VIA_SKILL=1 — mandatory; the PreToolUse hook blocks git commit without this marker.CLAUDE_COMMIT_VIA_SKILL=1 git commit -m "$(cat <<'EOF' ... EOF)".Co-Authored-By: trailer — read the exact model name from the session system info (e.g. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>). Never guess; the system info is always present.git status --short after.