alihan/repomix
1
0
Fork 0
mirror of https://github.com/yamadashy/repomix.git synced 2025-06-11 00:25:54 +03:00
Code Issues Packages Projects Releases Wiki Activity

docs(claude): Add dialogue type summaries to commit message format

Browse Source 
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 <noreply@anthropic.com>
This commit is contained in:
Kazuki Yamada
2025-06-08 18:09:47 +09:00
parent 19476abfcb
commit 65e602158e
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
CLAUDE.md
View File

@@ -121,13 +121,13 @@ npm run test
- Follow [Conventional Commits](https://www.conventionalcommits.org/) with scope: `type(scope): Description` - Follow [Conventional Commits](https://www.conventionalcommits.org/) with scope: `type(scope): Description`
- Write detailed commit messages focusing on the "why" rather than the "what" - 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 - **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 - Format: Use title for technical change, body with clear dialogue section marker and summary
- Start dialogue section with header like "Generated from the following user dialogue:" or "Based on user conversation:" - Start with dialogue type summary, then provide bullet points of the conversation flow
- Examples: - Examples:
``` ```
feat(cli): Add new --no-progress flag 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 - User requested disabling progress output for CI environments
- Progress output creates noise in build logs - Progress output creates noise in build logs
- Assistant implemented --no-progress flag for automation compatibility - Assistant implemented --no-progress flag for automation compatibility
@@ -137,9 +137,9 @@ npm run test
Co-Authored-By: Claude <noreply@anthropic.com> Co-Authored-By: Claude <noreply@anthropic.com>
``` ```
``` ```
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?" - User asked: "Is token counting only used for top files display?"
- Assistant explained multiple use cases including total output size - Assistant explained multiple use cases including total output size
- User suggested: "Since chars and tokens correlate, pre-filter by chars first" - User suggested: "Since chars and tokens correlate, pre-filter by chars first"