hivellm/Rulebook Terse Commit
templates/skills/core/rulebook-terse-commit/SKILL.md
Terse Conventional Commits generator. Subject ≤50 chars (hard cap 72), body only when 'why' isn't obvious, no filler. Use when user says 'write a commit', 'generate commit', 'commit message', or invokes /rulebook-terse-commit. Independent of the base rulebook-terse mode.
$ install --global
skillsauthnpx skillsauth add hivellm/rulebook Rulebook Terse CommitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 30, 2026, 2:40 AM8.4s1 file scanned
SKILL.md
- name:
- Rulebook Terse Commit
- description:
- Terse Conventional Commits generator. Subject ≤50 chars (hard cap 72), body only when 'why' isn't obvious, no filler. Use when user says 'write a commit', 'generate commit', 'commit message', or invokes /rulebook-terse-commit. Independent of the base rulebook-terse mode.
- version:
- 1.0.0
- category:
- core
- author:
- Rulebook
- tags:
- ["core", "git", "commits", "tokens"]
- dependencies:
- []
- conflicts:
- []
<!-- RULEBOOK_TERSE_COMMIT:START -->
Rulebook Terse Commit
Write commit messages terse and exact. Conventional Commits format. Why over what.
Subject line
- Format:
<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".
- Target ≤50 chars. Hard cap 72.
- No trailing period.
- Match project capitalization convention after the colon (match the repo's existing history).
Body
- Skip the body entirely when the subject is self-explanatory.
- Add a body ONLY for: non-obvious
why, breaking changes, migration notes, linked issues. - Wrap at 72 chars.
- Bullets use
-, not*. - Reference issues/PRs at the end:
Closes #42,Refs #17.
Never include
- "This commit does X", "I", "we", "now", "currently" — the diff says what.
- "As requested by ..." — use the
Co-authored-bytrailer instead. - "Generated with Claude Code" or any AI attribution.
- Emoji (unless project convention requires them).
- Restating the file name when
<scope>already identifies it.
Auto-Clarity
Always include a body for:
- Breaking changes (
!suffix on type, plusBREAKING CHANGE:footer). - Security fixes (CVE ID when applicable).
- Data migrations that touch user data.
- Reverts of a prior commit (reference the reverted SHA).
- Performance regressions fixed (include before/after numbers when possible).
Terseness is NEVER permitted to obscure these cases — future debuggers need the context.
Examples
New endpoint with non-obvious 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
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.
Simple bug fix — subject only
fix(auth): reject expired tokens on boundary second
Revert
revert: "feat(api): add GET /users/:id/profile"
This reverts commit a1b2c3d. Endpoint caused 5% latency regression
on the hot path; see incident INC-4219.
Boundaries
Only generates the commit message. Does NOT run git commit, does NOT stage files, does NOT amend. Output is a code block ready to paste.
Override: /rulebook-terse-commit off or "stop terse commit" reverts to the model's default commit style.
Related Skills
hivellm/analysis
research
VerifiedTrustedCommunity
Create structured analyses with numbered findings, execution plans, and task materialization
12SKILL.mdUpdated Apr 30, 2026
hivellm/spec
research
VerifiedTrustedCommunity
Author a rulebook task spec interactively — research, draft, ask the user clarifying questions, confirm, then create the tasks in rulebook ready for /rulebook-driver. Use when the user wants to plan/spec a feature before implementing.
11SKILL.mdUpdated Jun 1, 2026
hivellm/Karpathy Guidelines
development
VerifiedTrustedCommunity
Behavioral guidelines to reduce common LLM coding mistakes — overcomplication, sloppy refactors, hidden assumptions, weak goals. Use when writing, reviewing, or refactoring code. Auto-applies; invoke explicitly via /karpathy-guidelines or 'follow karpathy discipline'.
11SKILL.mdUpdated May 2, 2026
hivellm/Ralph Autonomous Loop
data-ai
VerifiedTrustedCommunity
Autonomous AI agent loop for iterative task implementation (@hivehub/rulebook ralph)
11SKILL.mdUpdated Apr 30, 2026