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 -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