Caveman Commit

作者 juliusbrussee2e08b9177c07無授權條款110K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫今天更新

Write a Conventional Commits message compressed to intent only. Use for "write a commit", "commit message", /commit or /caveman-commit.

AI 產生的概覽

撰寫精簡的 Conventional Commits 提交訊息,含主旨行與選用內文,可直接貼上。

功能
此技能依 Conventional Commits 格式產生提交訊息,只保留意圖。它訂定主旨行的規則(類型、選用範圍、祈使語氣摘要、長度限制),以及選用內文的規則,用於說明不明顯的理由、破壞性變更、移轉說明與問題引用。它以程式碼區塊輸出可直接貼上的訊息,且不會執行 git commit、暫存檔案或修訂提交。
適用情境
當被要求撰寫提交訊息,或使用者呼叫 commit、caveman-commit 時使用。適合遵循 Conventional Commits 且希望訊息簡短精確的專案。
執行需求
除代理外無需其他條件;僅為指示,不附帶指令碼。

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 payloadto 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/checkoutbefore 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位於skills/caveman-commit提交2e08b91

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架