Cursor rule

1---
2description: "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."
3alwaysApply: false
4---
5 
6# Commit Message
7> **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.'
8 
9 
10## Modes
11 
12- Default: standard Conventional Commits message
13- --fix-type: Forces type=fix. Use when commit type is unambiguous.
14 
15## What "last chat" means
16 
17- **Primary source of truth:** `git status`, `git diff` (unstaged), and `git diff --cached` (staged). Run these in the repo root (or the paths the user changed).
18- **Context:** use the current conversation to summarize *intent* and to spot **breaking** API/behavior changes that diff alone may not show.
19- If the user tracks a session baseline (e.g. branch, tag, or `git stash create` at start), you may `git diff <baseline>..HEAD` plus uncommitted diffs; otherwise use only the index and working tree.
20 
21## Quick workflow
22 
231. **Inventory** — List changed paths; group by feature vs chore vs docs vs test-only.
242. **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.
253. **Classify for semantic release** — `fix` → patch, `feat` → minor, **breaking** → major.
264. **Write the message** — `type(optional-scope)!: description` (see [REFERENCE.md](REFERENCE.md#message-format)). Use `!` or a `BREAKING CHANGE:` footer when behavior contracts change.
275. **Note defensive-code categories touched** — from CONVENTIONS.md: Rate limit | Retry with backoff | Circuit breaker | Timeout | Graceful degradation
286. **Note fix-ratio contribution** — Each `fix:` commit counts toward `metrics.commit_ratio.fix` in `specs/state.yaml`. After `release-branch`, `session-state` recalculates the ratio automatically. A high fix rate (>30%) triggers a deploy + smoke-test suggestion.
297. **Deliver** — Output:
30   - Proposed **full commit message** (title + optional body + footers).
31   - **Release bump** this commit would drive: `patch` | `minor` | `major` | `none`.
32   - Optional `git add …` and `git commit -m` instructions; do **not** run destructive git commands unless the user asked.
33 
34## Checklist before finalizing
35 
36- [ ] Type matches the **dominant** user-visible outcome (`feat` vs `fix` vs `perf`, etc.).
37- [ ] **Scope** is a short noun in parentheses if it helps (e.g. `fix(api): …`).
38- [ ] Breaking changes are explicit (`!` and/or `BREAKING CHANGE:` in the body/footer).
39- [ ] Description is imperative, lowercase start after the prefix, no trailing period in the title line.
40- [ ] **NO `Co-authored-by` or `Co-Authored-By` footers** — P1 rule (CONVENTIONS.md § Git Attribution). All commits must appear as if authored solely by the human user. The git hook and `land-branch.sh` both block these.
41 
42## When not to invent a bump
43 
44If 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](REFERENCE.md#custom-repositories).
45 
46## Further reading
47 
48- [REFERENCE.md](REFERENCE.md) — Message shape, footers, release mapping, squashing notes.
49 
50 
51 
52## Handoff
53 
54Gate: READY -> next: release-branch
55Writes: state.yaml handoff.next_skill = release-branch
56 
57---
58 
59# Conventional Commits + semantic-style release (reference)
60 
61## Message format
62 
63From [Conventional Commits 1.0.0](https://www.conventionalcommits.org/en/v1.0.0/#specification):
64 
65```text
66<type>[optional scope][optional !]: <description>
67 
68[optional body]
69 
70[optional footer(s)]
71```
72 
73- **Scope:** parenthesized noun, e.g. `feat(parser): …`.
74- **Breaking:** `!` before `:` (e.g. `feat(api)!: …`) and/or footer `BREAKING CHANGE: description` (token must be uppercase per spec for that footer name).
75- **Description:** short summary; body explains *why* or migration steps.
76 
77Common **types** (not exhaustive): `feat`, `fix`, `docs`, `style`, `refactor`, `perf`, `test`, `build`, `ci`, `chore` — as in [Angular / commitlint conventions](https://github.com/conventional-changelog/commitlint).
78 
79## Advanced Specification Patterns
80 
81### Reverts
82If 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>.`.
83 
84```text
85revert: feat(api): add user endpoint
86 
87This reverts commit 676104e.
88```
89 
90### Breaking Changes
91A breaking change can be signaled by:
921.  A **`BREAKING CHANGE:`** footer (must be uppercase, at the start of the footer). This is the **most compatible** way to trigger a Major release in `semantic-release` (Angular preset).
932.  A **`!`** after the type/scope: `feat(api)!: change user response shape`.
94 
95**Pro-tip:** For maximum compatibility with all tooling (older and newer), use BOTH the `!` and the `BREAKING CHANGE:` footer.
96 
97### Footers (Tokens & Values)
98Footers follow the same `Token: value` pattern as Git Trailers. Common tokens:
99- `Refs: #123`
100- `See-also: docs/ADR-001.md`
101- `Signed-off-by: Name <email>`
102 
103**Multi-line footers:** If a footer value spans multiple lines, each subsequent line must be indented.
104 
105### Squashing & History
106When using `gh pr merge --squash`, the PR title is usually used as the commit subject. 
107- **PR Title:** MUST follow `<type>(<scope>): <description>`
108- **PR Body:** Content will be moved to the commit body.
109 
110## Release Type Mapping (Default Angular Preset)
111 
112This table reflects the **out-of-the-box** behavior of `semantic-release` using the `@semantic-release/commit-analyzer` default (Angular) rules.
113 
114| Commit pattern | Release | Notes |
115|----------------|---------|-------|
116| `fix:` | **Patch** | Bug fixes |
117| `feat:` | **Minor** | New features |
118| `perf:` | **Patch** | Performance improvements |
119| `any type` + `BREAKING CHANGE:` footer | **Major** | **Mandatory** for Major version bumps in default configs. |
120| `any type!:` (exclamation mark) | **Major** | Supported by modern CC parsers, but use footer for max safety. |
121| `docs:`, `chore:`, `test:`, `ci:`, `refactor:`, `style:` | **None** | Does not trigger a new release by default. |
122 
123> **Warning:** While `refactor:` and `style:` improve code, they do NOT trigger a release in the default Angular preset. Use `fix:` if a refactor also fixes a bug, or `feat:` if it adds new behavior.
124 
125## Custom Repositories
126 
127- Read `release.config.js`, `.releaserc`, or `package.json` → `release` / `semantic-release` config.
128- The **@semantic-release/commit-analyzer** preset may map types differently; prefer **their** rules when they conflict with this reference.
129 
130## Squash and PR titles
131 
132- If the team squashes on merge, the **PR title** often becomes the single squashed commit subject — it should still follow `type(scope): description` for tooling.
133- `revert:` type and `Refs:` footers are valid patterns; revert handling varies by [tooling](https://www.conventionalcommits.org/en/v1.0.0/#specification).
134 
135## Links
136 
137- [Conventional Commits — specification](https://www.conventionalcommits.org/en/v1.0.0/#specification)
138- [semantic-release — README (commit format & flow)](https://github.com/semantic-release/semantic-release#commit-message-format)
139- Automation and docs align with [semantic-release](https://github.com/semantic-release/semantic-release) upstream; a fork may be substituted without changing this guidance.
140