commit-message
Reviews working-tree changes, then drafts a Conventional Commits title/body and states the semantic-release version bump a single such commit would imply. Also notes which defensive-code categories were touched. Use when the user wants to commit recent work, prepare a Conventional Commits message, or asks for semantic-release / semver-consistent messaging before git commit.
danielvm-git · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add danielvm-git/bigpowers --skill commit-messageAbout this skill
name: commit-message model: haiku description: "Reviews working-tree changes, then drafts a Conventional Commits title/body and states the semantic-release version bump a single such commit would imply. Also notes which defensive-code categories were touched. Use when the user wants to commit recent work, prepare a Conventional Commits message, or asks for semantic-release / semver-consistent messaging before git commit."
story: e82s02
Commit Message
HARD GATE — HARD GATE — Commits must follow Conventional Commits spec (type(scope): description). Do NOT use vague messages like 'fix' or 'updates.' The message must explain the 'why,' not the 'what.'
Modes
- Default: standard Conventional Commits message
- --fix-type: Forces type=fix. Use when commit type is unambiguous.
What "last chat" means
- Primary source of truth: Read
state.yamlvcs.kind. Git usesgit status,git diff, andgit diff --cached; Jujutsu usesjj status,jj diff, andjj log -r @. Run in the repo root. - Context: use the current conversation to summarize intent and to spot breaking API/behavior changes that diff alone may not show.
- If the user tracks a session baseline (e.g. branch, tag, or
git stash createat start), you maygit diff <baseline>..HEADplus uncommitted diffs; otherwise use only the index and working tree.
Quick workflow
- Inventory — List changed paths; group by feature vs chore vs docs vs test-only.
- Decide commit shape — One atomic commit is ideal. If the diff mixes unrelated concerns, recommend multiple commits (each with its own type/scope) before suggesting one message.
- Classify for semantic release —
fix→ patch,feat→ minor, breaking → major. - Write the message —
type(optional-scope)!: description(see REFERENCE.md). Use!or aBREAKING CHANGE:footer when behavior contracts change. - Note defensive-code categories touched — from CONVENTIONS.md: Rate limit | Retry with backoff | Circuit breaker | Timeout | Graceful degradation
- Note fix-ratio contribution — Each
fix:commit counts towardmetrics.commit_ratio.fixinspecs/state.yaml. Afterrelease-branch,session-staterecalculates the ratio automatically. A high fix rate (>30%) triggers a deploy + smoke-test suggestion. - Deliver — Output:
- Proposed full commit message (title + optional body + footers).
- Release bump this commit would drive:
patch|minor|major|none. - Optional native command: Git
git commit -m; Jujutsujj commit -m. Never omit-mor run destructive commands unless asked.
Checklist before finalizing
- Type matches the dominant user-visible outcome (
featvsfixvsperf, etc.). - Scope is a short noun in parentheses if it helps (e.g.
fix(api): …). - Breaking changes are explicit (
!and/orBREAKING CHANGE:in the body/footer). - Description is imperative, lowercase start after the prefix, no trailing period in the title line.
- NO
Co-authored-byorCo-Authored-Byfooters — P1 rule (CONVENTIONS.md § Git Attribution). All commits must appear as if authored solely by the human user. The git hook andland-branch.shboth block these.
When not to invent a bump
If the repo uses a custom @semantic-release/commit-analyzer preset, note that your bump is heuristic and they should match .releaserc / release.config.*. See REFERENCE.md.
Further reading
- REFERENCE.md — Message shape, footers, release mapping, squashing notes.
Handoff
Gate: READY -> next: release-branch Writes: state.yaml handoff.next_skill = release-branch
Conventional Commits + semantic-style release (reference)
Message format
From Conventional Commits 1.0.0:
<type>[optional scope][optional !]: <description>
[optional body]
[optional footer(s)]
- Scope: parenthesized noun, e.g.
feat(parser): …. - Breaking:
!before:(e.g.feat(api)!: …) and/or footerBREAKING CHANGE: description(token must be uppercase per spec for that footer name). - Description: short summary; body explains why or migration steps.
Common types (not exhaustive): feat, fix, docs, style, refactor, perf, test, build, ci, chore — as in Angular / commitlint conventions.
Advanced Specification Patterns
Reverts
If the commit reverts a previous commit, it should begin with revert:, followed by the header of the reverted commit. In the body, it should say: This reverts commit <hash>..
revert: feat(api): add user endpoint
This reverts commit 676104e.
Breaking Changes
A breaking change can be signaled by:
- A
BREAKING CHANGE:footer (must be uppercase, at the start of the footer). This is the most compatible way to trigger a Major release insemantic-release(Angular preset). - A
!after the type/scope:feat(api)!: change user response shape.
Pro-tip: For maximum compatibility with all tooling (older and newer), use BOTH the ! and the BREAKING CHANGE: footer.
Footers (Tokens & Values)
Footers follow the same Token: value pattern as Git Trailers. Common tokens:
Refs: #123See-also: docs/ADR-001.mdSigned-off-by: Name <email>
Multi-line footers: If a footer value spans multiple lines, each subsequent line must be indented.
Squashing & History
When using gh pr merge --squash, the PR title is usually used as the commit subject.
- PR Title: MUST follow
<type>(<scope>): <description> - PR Body: Content will be moved to the commit body.
Release Type Mapping (Default Angular Preset)
This table reflects the out-of-the-box behavior of semantic-release using the `@semantic-release/com