From 961484f5178ec18b90f4bc046e45c431f91d9063 Mon Sep 17 00:00:00 2001 From: Oscar Wallberg Date: Thu, 7 May 2026 16:41:24 +0200 Subject: [PATCH] fix(claude): mention sub-scopes for commits --- .claude/CLAUDE.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/.claude/CLAUDE.md b/.claude/CLAUDE.md index 204e469..fd759cd 100644 --- a/.claude/CLAUDE.md +++ b/.claude/CLAUDE.md @@ -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). +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. Don't retroactively rewrite committed history unless the user explicitly asks. - -### No Co-Authored-By Claude line - -Don't add `Co-Authored-By: Claude ... ` (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.