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 -12
View File
@@ -123,18 +123,9 @@ artificially split what was done as one action.
### Commit message format
Follow Conventional Commits and match the repo's existing style:
```
<type>(<scope>): <short description>
<optional body — what and why, not how>
```
Types: `feat`, `fix`, `refactor`, `chore`, `docs`, `test`, `style`, `perf`
Keep the first line under 72 characters. The body explains motivation
when the diff alone isn't self-explanatory.
Follow `$HOME/.claude/lib/commit-message.md`: the project's documented
convention if there is one, else a short message (50 words max, medium
technical level). Run its lookup once for the whole plan.
### Capitalize candidates (draft only — decided later, written in `MODE: apply`)