메뉴
Use when writing git commit messages, especially when ARCS Caveman mode is active. Produces Conventional Commits with terse, intent-preserving prose. Subject ≤50 chars; body only when the "why" isn't obvious from the diff.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when the user provides a GitHub PR link with a "deep review" trigger inside a locally cloned repo, to perform a thorough multi-dimensional code review grounded in ARCS DAG context, AGENTS.md conventions, and optional codegraph coupling analysis, then post findings as inline GitHub review comments under explicit user gate
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when initializing a new ARCS project — bootstrapping a repo into the DAG with metadata, docs, and structural knowledge entries. Covers gather → present summary → init → codegraph ingestion → fan-out analysis across typed sub-agents.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
| name | caveman-commit |
| description | Use when writing git commit messages, especially when ARCS Caveman mode is active. Produces Conventional Commits with terse, intent-preserving prose. Subject ≤50 chars; body only when the "why" isn't obvious from the diff. |
Writing git commit messages. Terse, exact, Conventional Commits. Why over what.
flowchart TD
A[Read diff] --> B[Classify: feat/fix/refactor/perf/docs/test/chore]
B --> C["Write subject: type(scope): imperative ≤50"]
C --> D{Why obvious from diff?}
D -->|yes| E[Subject only — done]
D -->|no| F[Write body: why + context]
F --> G{Breaking/security/migration?}
G -->|yes| H[MUST include body]
G -->|no| E
H --> E
| Element | Rule |
|---|---|
| Subject | <type>(<scope>): <imperative> ≤50 chars (hard cap 72) |
| Types | feat, fix, refactor, perf, docs, test, chore, build, ci, style, revert |
| Mood | Imperative: "add", "fix", "remove" — not past/present tense |
| Body | Wrap 72 chars, bullets -, skip if subject self-explanatory |
| Issues | End of body: Closes #42, Refs #17 |
git commit