القائمة
Use when the user asks for a commit message, wants a Conventional Commit, or wants a terse commit subject that fits in fifty characters and focuses on why over what.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user wants the laziest solution that actually works — types /ponytail, says "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Supports intensity levels lite, full, ultra (default). Pairs with caveman, which compresses prose, not code.
Use when the user wants a whole-repo audit for over-engineering — says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", or invokes /ponytail-audit. Like ponytail-review but scans the entire tree, not a diff. One-shot report, applies no fixes. Gated by the ponytail audit_ponytail component.
Use when the user wants to harvest every `ponytail:` comment in the codebase into a tracked debt ledger — says "ponytail debt", "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail ledger", or "what did we mark to do later". One-shot report, changes nothing. Gated by the ponytail debt_ponytail component.
Use when the user asks how ponytail mode works, what intensity levels exist, what the slash commands are, how to toggle it, or wants a quick-reference card before turning the mode on. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".
Use when the user wants a code review focused exclusively on over-engineering — says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness/security review; this one only hunts complexity in the current diff. Gated by the ponytail review_ponytail component.
Use when navigating an unfamiliar codebase, tracing how code connects (callers, dependencies, the blast radius of a change), or whenever the repo ships a graphify-out/graph.json knowledge graph. Query the graph before grepping/reading raw source for orientation.
| name | caveman-commit |
| description | Use when the user asks for a commit message, wants a Conventional Commit, or wants a terse commit subject that fits in fifty characters and focuses on why over what. |
| license | MIT |
| metadata | {"author":"ai-playbook (ported from JuliusBrussee/caveman, MIT)","version":"1.0"} |
Write commit messages that are short, conventional, and focused on intent.
User intent triggers (any of):
Always emit a Conventional Commit. Shape:
<type>(<scope>): <subject>
<body — optional, only if subject does not capture the why>
Rules:
<type> ∈ feat | fix | refactor | perf | docs | test | chore | build | ci | style.<scope> ≤ 14 chars, kebab-case, optional. Drop the parentheses if no scope.<subject> ≤ 50 chars, lowercase, no trailing period. Imperative voice ("add", not "added"/"adds").<body> only when the subject cannot fit the why. Wrap at 72 chars. Caveman style: drop articles, fragments OK.Read the diff. Run git diff --cached (staged) or git diff (unstaged) — whichever the user pointed at. If both are empty, refuse with Nothing staged or modified to commit.
Identify intent. What is the user trying to accomplish? Look at:
Pick the type.
feat.fix.refactor.perf.docs.test.build/ci/chore.Pick the scope. Usually a directory or module name from the changed paths. Drop if scope spans multiple unrelated areas.
Write the subject — why over what.
fix(auth): change <to<= in token expiry checkfix(auth): close one-second token expiry gapfeat: add new endpointfeat(api): support batch user lookupAdd a body only if needed. If the subject explains the why, skip the body. Otherwise add a 1-2 sentence caveman-style paragraph.
git commit..env, or large diffs in the body.feat(toggle): per-project caveman state at .ai-playbook/caveman.json
fix(mcp): guard against missing caveman-shrink binary
npx caveman-shrink absent on offline machines. Wrap call in
try/except, warn once, fall through to un-wrapped command.
refactor(scripts): single source of truth for skill descriptions