‹ 首页

caveman-commit

@juliusbrussee · 收录于 1 周前 · 上游提交 1 周前

Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.

适合你,如果每次写提交信息都要纠结很久

/ 通过 npx 安装 校验哈希
npx oh-my-skill add juliusbrussee/caveman/caveman-commit
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- juliusbrussee/caveman/caveman-commit
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify juliusbrussee/caveman/caveman-commit
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
87334GitHub stars
~566最小装载
~566含声明引用
~841文本包总量
索引托管

怎么用

商店整理自技能原文 · 版本 0d95a81 · 表述以原文为准
它做什么

安装后,Claude 会生成极简的 Git 提交信息,采用 Conventional Commits 格式,主题行不超过 50 字符,仅在必要时添加正文。

什么时候触发

当你说“write a commit”、“commit message”、“generate commit”、“/commit”或“/caveman-commit”时触发;检测到暂存区有变更时自动触发。

装好后可以这样说
Claude 会根据暂存区变更生成提交信息。
Claude 会生成类型为 fix 的提交信息。
Claude 会恢复为冗长的提交风格。
技能原文 SKILL.md作者撰写 · MIT · 0d95a81

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.

按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。