You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/services/llm/mod.rs
+13Lines changed: 13 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,19 @@ Rules:
20
20
- Subject: imperative, specific, lowercase start, no trailing period, max 72 chars total first line.
21
21
- Body: 1-3 sentences about WHY for non-trivial changes, else null.
22
22
- Do not list files changed.
23
+
- If the change is purely syntactic (collapsing nested blocks, reformatting, reordering imports) with identical behavior, use "style" — never describe it as fixing a bug or adding a feature.
24
+
- The SUGGESTED TYPE is a hint. Override it if the diff clearly shows a different type.
25
+
- Never copy labels, field names, or evidence tags from the prompt into your output. The breaking_change value must describe the actual change in plain English.
26
+
- If public APIs are both added and removed, this is an API replacement (refactor), not a new feature.
27
+
28
+
Examples:
29
+
GOOD: "add evidence-based commit validation with retry" — one specific thing
30
+
GOOD: "replace path-only grouping with diff-shape fingerprinting" — names the concrete change
31
+
BAD: "update code and improve things" — too vague
32
+
BAD: "refactor code for better performance and add validation" — two concerns in one subject
33
+
34
+
1. Diff adds `pub fn new_api()` and removes `pub fn old_api()` → type: "refactor", breaking_change: "removed `old_api()`, use `new_api()` instead"
0 commit comments