feat(commits): follow project convention, else short messages

New lib/commit-message.md looks for a documented convention first. Without one, messages stay under 50 words at medium technical level.
This commit is contained in:
bchanot committed 2026-10-16 11:49:26 +02:00
1 parent eb1cfe55a9
commit e91dcb3f12
8 files changed
+58 -31

No files matched your search

+3 -7
View File
@@ -223,13 +223,9 @@ Parse the `BUGFIX-EXEC REPORT`:
- `skip` → leave changes uncommitted, exit cleanly.
- `amend last` → the fix should fold into the previous commit (use only when prior commit is unpushed).
3. Commit using conventional format (after approval):
```
fix(<scope>): <root cause description>
<what was wrong and why>
<what the fix does>
```
3. Commit after approval, message per `$HOME/.claude/lib/commit-message.md`
(project convention first, else short: root cause in the subject, at most
two sentences of body).
4. Print summary:
```
BUGFIX COMPLETE
+3 -6
View File
@@ -191,12 +191,9 @@ run + one verifier + one security dispatch.
## STEP 5 — COMMIT
Commit using conventional format:
```
feat(<scope>): <what was added>
<brief description of the feature>
```
Commit with the message per `$HOME/.claude/lib/commit-message.md`
(project convention first, else short: what was added, at most two
sentences of body).
If the feature touched multiple concerns (e.g., feature + config +
test), consider splitting into 2-3 atomic commits grouped by logical
+3 -4
View File
@@ -190,10 +190,9 @@ Parse the `HOTFIX-EXEC REPORT`:
- Structural failure (mute / unparsable / no VERDICT line) → treat as a
failed gate: retry ONCE fresh; a 2nd structural failure → revert +
escalate. A mute auditor is never a PASS.
3. Commit using conventional format (only after smoke AND security pass):
```
fix(<scope>): <what was wrong>
```
3. Commit only after smoke AND security pass, message per
`$HOME/.claude/lib/commit-message.md` (no convention: one subject line,
`fix(<scope>): <what was wrong>`).
4. Print summary:
```
HOTFIX APPLIED