caveman-commit

作者: juliusbrussee

超壓縮提交訊息生成器。去除提交訊息中的雜訊,同時保留意圖與理由。採用 Conventional Commits 格式。主旨不超過50字元,僅在「原因」不明顯時加入內文。當使用者說「寫提交」、「提交訊息」、「生成提交」、「/commit」或呼叫 /caveman-commit 時使用。暫存變更時自動觸發。

npx skills add https://github.com/juliusbrussee/caveman --skill caveman-commit

Write commit messages terse and exact. Conventional Commits format. No fluff. Why over what.

Rules

Subject line:

  • <type>(<scope>): <imperative summary><scope> optional
  • Types: feat, fix, refactor, perf, docs, test, chore, build, ci, style, revert
  • Imperative mood: "add", "fix", "remove" — not "added", "adds", "adding"
  • ≤50 chars when possible, hard cap 72
  • No trailing period
  • Match project convention for capitalization after the colon

Body (only if needed):

  • Skip entirely when subject is self-explanatory
  • Add body only for: non-obvious why, breaking changes, migration notes, linked issues
  • Wrap at 72 chars
  • Bullets - not *
  • Reference issues/PRs at end: Closes #42, Refs #17

What NEVER goes in:

  • "This commit does X", "I", "we", "now", "currently" — the diff says what
  • "As requested by..." — use Co-authored-by trailer
  • "Generated with Claude Code" or any AI attribution — unless the user's own rule requires an Assisted-by/AI-attribution trailer, then add it as a trailer
  • Emoji (unless project convention requires)
  • Restating the file name when scope already says it

Examples

Diff: new endpoint for user profile with body explaining the why

  • ❌ "feat: add a new endpoint to get user profile information from the database"
  • 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.
    

Auto-Clarity

Always include body for: breaking changes, security fixes, data migrations, anything reverting a prior commit. Never compress these into subject-only — future debuggers need the context.

Boundaries

Only generates the commit message. Does not run git commit, does not stage files, does not amend. Output the message as a code block ready to paste. "stop caveman-commit" or "normal mode": revert to verbose commit style.

來自 juliusbrussee 的更多技能

caveman
juliusbrussee
超壓縮溝通模式。透過穴居人式簡潔表達,減少約75%的token使用量,同時維持完整技術準確性。支援強度等級:lite、full(預設)、ultra、wenyan-lite、wenyan-full、wenyan-ultra。當使用者說「caveman mode」、「talk like caveman」、「use caveman」、「less tokens」、「be brief」或呼叫/caveman時啟用。亦會在要求token效率時自動觸發。
communicationproductivity
caveman-compress
juliusbrussee
將自然語言記憶檔案(CLAUDE.md、待辦事項、偏好設定)壓縮成穴居人格式以節省輸入令牌。保留所有技術內容、程式碼、網址與結構。壓縮版本會覆蓋原始檔案。人類可讀的備份會另存為FILE.original.md。觸發指令:/caveman-compress FILEPATH 或「壓縮記憶檔案」
developmentdocument
caveman-help
juliusbrussee
所有穴居人模式、技能與指令的快速參考卡。一次性顯示,非持續模式。觸發方式:/caveman-help、「caveman help」、「what caveman commands」、「how do I use caveman」。
developmentdocumentproductivity
caveman-review
juliusbrussee
超壓縮程式碼審查評論。減少PR回饋中的雜訊,同時保留可執行的關鍵資訊。每條評論僅一行:位置、問題、修正。當使用者說「審查此PR」、「程式碼審查」、「審查差異」、「/review」或呼叫/caveman-review時使用。審查拉取請求時自動觸發。
developmentcode-review
caveman-stats
juliusbrussee
顯示當前會話的實際Token使用量與預估節省金額。直接從Claude Code會話日誌讀取,無需AI估算。透過/caveman-stats觸發。輸出由mode-tracker鉤子注入,模型本身不計算數值。
developmentdata-analysis
cavecrew
juliusbrussee
Decision guide for delegating to caveman-style subagents. Tells the main thread WHEN to spawn `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit), or `cavecrew-reviewer` (diff review) instead of doing the work inline or using vanilla `Explore`. Subagent output is caveman-compressed so the tool-result injected back into main context is ~60% smaller — main context lasts longer across long sessions. Trigger: "delegate to subagent", "use cavecrew", "spawn...
developmentcode-reviewapi