菜单
Use when writing a commit message — "write a commit", "commit message", "generate commit", "/commit", or invokes /faceless-commit, or when staging changes. Legacy alias: "/caveman-commit".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user wants a plan or design stress-tested before implementation, or asks to be grilled, interviewed, or interrogated about a decision tree.
Disciplined root-cause investigation for hard bugs and performance regressions, with findings pinned to the case board. Use when user reports a bug, says something is broken/throwing/failing, describes a performance regression, or asks to diagnose/debug/investigate something.
Use when reviewing code or a diff — "review this PR", "code review", "review the diff", "/review", or invokes /faceless-review. Legacy alias: "/caveman-review".
Use when the user wants terse, compressed, low-token responses — "faceless mode", "talk faceless", "be brief", "less tokens", "compress", or invokes /faceless. Also when token efficiency is explicitly requested. Legacy aliases: "caveman mode", "use caveman".
Use when turning raw material — research, notes, interview answers, fragments, or investigation findings — into a sourced written report or article, or when shaping, drafting, restructuring, or tightening such a draft. Triggers: "write up the findings", "investigative report", "turn these notes into an article", "draft the report", "shape this into an article", "edit the article", "help me write this up".
Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `investigate`, `tdd`, `improve-codebase-architecture`, or `zoom-out` -- or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.
| name | faceless-commit |
| description | Use when writing a commit message — "write a commit", "commit message", "generate commit", "/commit", or invokes /faceless-commit, or when staging changes. Legacy alias: "/caveman-commit". |
| triggers | ["write a commit","commit message","generate commit","/commit","/faceless-commit"] |
| category | faceless |
| token_efficiency | high |
| dependencies | [] |
Commit messages terse and exact. Conventional Commits. No fluff. Why over what — the diff already says what.
Subject line:
<type>(<scope>): <imperative summary> — <scope> optionalfeat, fix, refactor, perf, docs, test, chore, build, ci, style, revertBody (only if needed):
- not *Closes #42, Refs #17Never goes in:
Co-authored-by trailerDiff: new endpoint for user profile, body explains the why
feat(api): add GET /users/:id/profile
Mobile client needs profile data without the full user payload
to reduce LTE bandwidth on cold-launch screens.
Closes #128
Diff: breaking API change
feat(api)!: rename /v1/orders to /v1/checkout
BREAKING CHANGE: clients on /v1/orders must migrate to /v1/checkout
before 2026-06-01. Old route returns 410 after that date.
Always include a body for: breaking changes, security fixes, data migrations, anything reverting a prior commit. Never compress these into subject-only — future debuggers need the context.
Only generates the message. Does not run git commit, does not stage, does not amend. Output
the message as a code block ready to paste. "stop faceless-commit" / "normal mode": revert to
verbose commit style.