메뉴
MUST be used for every git commit. Formats Conventional Commit messages, checks for breaking changes, and stages files atomically.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Exercise software as real consumer would — docs-first walkthrough, full public surface coverage, adversarial misuse — producing a ranked friction report. Works for any software type (library, CLI, server/API, web UI, TUI). Use when user says "dogfood", "exercise as a consumer/user", "friction report", "consumer trial", "try it like a real user", or as harden skill Phase 1 (Exercise → friction). Re-eval mode re-runs a prior report for a resolved/still-live delta.
Iterative refinement loop for taking a change to a high quality bar. Sequences exercise→friction, grill→decide, TDD slices, then review→soundness→simplify→architecture→test-health→docs passes — repeating until a full round finds nothing significant — under fixed discipline (authority docs sacred, commit per slice, verify every slice, reverse your own calls on evidence, capture decisions durably). Use when the user wants to build or refine something "properly", harden a change, run a multi-pass quality loop, evaluate an API as a real consumer, or asks to "harden", "do this properly", "full quality pass", "refine loop", "keep going until clean", or "production-grade" work. Gated — stops for the user's call at authority conflicts, fix decisions, architecture do/decline, and irreversible actions.
Collaborative specification refinement through codebase analysis, discovery interviews, and iterative red-teaming. Use when user wants to write a spec, refine requirements, design a feature, or mentions "spec", "requirements", "PRD", or "specification".
Break a plan or spec into vertical-slice tasks. Use when user wants to break down work into tasks, slice a spec into implementable pieces, or mentions "to-tasks", "break down", "task breakdown", or "slice".
Audit and improve a user-facing entry doc (README, docs-site landing, man-page intro, getting-started guide) for factual accuracy and for three reader audiences — evaluator, newcomer, returner. Use when asked to "improve/proofread/audit the readme (or docs)", "is my readme any good", "make the docs clearer / more motivating", or to check docs for stale/inaccurate information.
Review changed code for reuse, quality, and efficiency, then fix any issues found. Understands before touching, guards against over-simplification.
| name | commit |
| description | MUST be used for every git commit. Formats Conventional Commit messages, checks for breaking changes, and stages files atomically. |
Message format: Conventional Commits v1.0.0 (<type>(<scope>): <description>).
! AND a BREAKING CHANGE: footer. Pre-1.0.0, breaking changes bump MINOR, not MAJOR.Co-Authored-By:) or any agent-attribution trailer to the message.Stage atomically — other agents may edit files in parallel. Commit only files you touched, each path explicit:
# tracked files
git commit -m "<message>" -- path/to/file1 path/to/file2
# brand-new files
git restore --staged :/ && git add "path/to/file1" "path/to/file2" && git commit -m "<message>" -- path/to/file1 path/to/file2