warg/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(claude): mention sub-scopes for commits

Browse Source
This commit is contained in:
Oscar Wallberg
2026-05-07 16:41:24 +02:00
parent 4cb787e420
commit 961484f517
1 changed files with 2 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude/CLAUDE.md
+2 -4
View File
@@ -72,10 +72,8 @@ Common types:
Subject line: imperative, lowercase after the colon, no trailing period, aim for <= 72 chars. Body paragraphs explain the *why*, not the *what* (the diff shows the what). Subject line: imperative, lowercase after the colon, no trailing period, aim for <= 72 chars. Body paragraphs explain the *why*, not the *what* (the diff shows the what).
Scope may use slash-separated subscopes (`fix(parser/lexer)`, `feat(api/auth)`) when the precision adds information about which submodule changed. Flat scopes (`fix(parser)`) are fine for broader changes. Inconsistency between commits is acceptable — subscope depth doesn't need to be uniform.
Breaking changes: append `!` to the type or scope (`feat(api)!: ...`) and include a `BREAKING CHANGE:` footer when the change needs explanation. Breaking changes: append `!` to the type or scope (`feat(api)!: ...`) and include a `BREAKING CHANGE:` footer when the change needs explanation.
Don't retroactively rewrite committed history unless the user explicitly asks. Don't retroactively rewrite committed history unless the user explicitly asks.
### No Co-Authored-By Claude line
Don't add `Co-Authored-By: Claude ... <noreply@anthropic.com>` (or any Claude co-author trailer) to commit messages. End the commit with the actual content. The user finds the trailer adds clutter without serving any audience.