From 65e602158e1af38ec8b758409865f552d7d5e31b Mon Sep 17 00:00:00 2001 From: Kazuki Yamada Date: Sun, 8 Jun 2025 18:09:47 +0900 Subject: [PATCH] docs(claude): Add dialogue type summaries to commit message format MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit User requested clarification on commit message dialogue format: - User wanted dialogue type/nature to be summarized upfront - User preferred descriptive headers like 'User requested feature enhancement' - Assistant added dialogue type summaries before bullet points - Examples now show 'feature enhancement for CI automation' and 'performance optimization discussion' - Makes the nature of user-AI collaboration immediately clear 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude --- CLAUDE.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index 49e959a..74f8f34 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -121,13 +121,13 @@ npm run test - Follow [Conventional Commits](https://www.conventionalcommits.org/) with scope: `type(scope): Description` - Write detailed commit messages focusing on the "why" rather than the "what" - **Include user dialogue context**: Reference the specific conversation or request that led to the change in the commit body -- Format: Use title for technical change, body with clear dialogue section marker -- Start dialogue section with header like "Generated from the following user dialogue:" or "Based on user conversation:" +- Format: Use title for technical change, body with clear dialogue section marker and summary +- Start with dialogue type summary, then provide bullet points of the conversation flow - Examples: ``` feat(cli): Add new --no-progress flag - Generated from the following user dialogue: + User requested a feature enhancement for CI automation: - User requested disabling progress output for CI environments - Progress output creates noise in build logs - Assistant implemented --no-progress flag for automation compatibility @@ -137,9 +137,9 @@ npm run test Co-Authored-By: Claude ``` ``` - perf(metrics): Optimize token counting for top files + perf(metrics): Optimize token counting performance optimization discussion: - Based on user conversation: + User questioned current token counting approach and suggested improvements: - User asked: "Is token counting only used for top files display?" - Assistant explained multiple use cases including total output size - User suggested: "Since chars and tokens correlate, pre-filter by chars first"