User pointed out formatting issue in documentation:
- Example had redundant 'performance optimization discussion' in title
- User requested cleaning up the example format
- Assistant removed duplicate text to show proper title format
- Example now shows clean 'perf(metrics): Optimize token counting for top files'
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
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>
Based on user conversation:
- User wanted dialogue part to be clearly distinguishable
- User suggested using headers like 'Generated from the following user dialogue:'
- User preferred bullet point format for dialogue summary
- Assistant updated examples to show clear section separation
- Makes it obvious which part contains user-AI conversation context
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
User: 'The current examples don't clearly show it's a dialogue'
Assistant: Added explicit 'User:' and 'Assistant:' markers to make
conversation flow more obvious in commit bodies.
User: 'Make it clear this is about dialogue'
Assistant: Updated examples to show actual conversation exchanges
with arrows (→) for quick actions and clear dialogue structure.
This makes commit messages more readable and the user-AI collaboration
context immediately apparent to future developers.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
User pointed out that dialogue context should be in the commit body,
not just the title. Updated examples to show proper format with
technical summary in title and user context/reasoning in body.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Specify that commit messages should reference the conversation/request that led to changes
- Provide examples showing how to connect commits to user interactions
- Improves traceability between user requests and code changes for future reference
- Reorder CLI Pack Summary to show 'Total Tokens' before 'Total Chars'
- Ensures consistency between CLI and website interfaces
- Completes the token-first display priority across all interfaces
- CLI: Change order from 'Total Chars, Total Tokens' to 'Total Tokens, Total Chars'
- Website: Change order from 'Total Size, Total Tokens' to 'Total Tokens, Total Size'
- Maintains consistency across interfaces by prioritizing token metrics
- Update TryItResultContent.vue to show tokens before chars
- Matches CLI display format: (tokens, chars, %) instead of (chars, tokens, %)
- Maintains consistency between CLI and website interfaces
- Update top files display format from '(chars, tokens, %)' to '(tokens, chars, %)'
- Emphasizes token count as primary metric since files are now ranked by tokens
- Maintains consistent ordering with the ranking logic
- Change character-based pre-filtering from 5x to 10x of display count
- Improves accuracy of token-based ranking while maintaining performance benefits
- Better balance between computational efficiency and ranking precision
- Add character-based pre-filtering to reduce token calculation overhead
- Implement calculateSelectiveFileMetrics for targeted token counting
- Only calculate tokens for top candidates (5x display count) instead of all files
- Maintain accurate token-based ranking while improving performance for large codebases
- Update tests to cover new selective calculation functionality
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Remove YouTubeVideo global component registration from VitePress theme
- Add direct YouTubeVideo imports in all language versions of index.md and guide/index.md
- Update video ID usage to centralized VIDEO_IDS.REPOMIX_DEMO constant
- Improve component modularity and maintainability across 24 documentation files
- Create YouTubeVideo.vue component with responsive design
- Register component globally in VitePress theme
- Add explanatory sections and video to all language versions of index.md
- Add video to all language versions of guide/index.md
- Support for 12 languages: en, ja, zh-cn, zh-tw, ko, de, fr, es, pt-br, vi, hi, id
- Improve user onboarding with visual demonstration of Repomix features
- Create useFileUpload composable for unified drag/drop, validation, and file processing
- Create useZipProcessor composable for ZIP file operations
- Refactor TryItFileUpload.vue: reduce from 213 to 105 lines (50% reduction)
- Refactor TryItFolderUpload.vue: reduce from 342 to 115 lines (66% reduction)
- Eliminate code duplication while maintaining all existing functionality
- Improve type safety with configurable validation and preprocessing pipelines
- Enable better reusability and testability of upload logic
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Create usePackOptions composable for pack configuration state
- Create usePackRequest composable for request lifecycle management
- Refactor TryIt.vue to use composables, reducing complexity from 19 refs to 2 composables
- Improve type safety with PackOptions interface and InputMode type
- Enable better reusability and testability of state logic
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add dedicated 'Pre-Commit Requirements (MANDATORY)' section
- Clearly specify npm run lint && npm run test as required before every commit
- Explain what each command does (Biome, TypeScript, Secretlint, full test suite)
- Emphasize never committing failing code
- Update Review Process Checklist to mark linting/testing as MANDATORY
- Reorganize Git Workflow section for better clarity
This ensures code quality and prevents broken commits from entering the repository.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Emphasize immediate documentation of learned patterns during development
- Add examples of valuable knowledge worth documenting (project quirks, tools, debug techniques)
- Provide guidelines for maintaining this file with specific, contextual information
- Stress that CLAUDE.md is a living document that should grow with each session
- Ensure knowledge continuity across different coding sessions
This will help preserve valuable insights and patterns discovered during
development tasks, making future work more efficient.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Highlight 'IMPORTANT\!' for conversation resolution step
- Add checklist for complete PR review process
- Emphasize that resolving conversations shows respect for reviewers
- Note that unresolved conversations can delay PR approval
- Add reminder about efficient PR management
This ensures future PRs properly resolve all feedback conversations.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add commands for viewing different types of PR comments (general, line-specific, reviews)
- Document automated review bots used in this repository (CodeRabbit, Gemini, Copilot, Codecov)
- Provide workflow for responding to review feedback with proper commit messages
- Include common review issues and solutions for Vue.js/frontend development
- Add guidance for resolving conversations and responding to reviewers
This will help with future PR review processes and ensure consistent
handling of automated review feedback.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add scroll event listener to hide tooltip when page scrolls
- Prevent tooltip detachment from button during scroll
- Add explicit mouseleave handler for better tooltip control
- Override CSS hover states with JavaScript for consistent behavior
- Use passive scroll listener for better performance
This addresses the medium-priority feedback about tooltip positioning
during scroll events, ensuring the tooltip maintains proper association
with the button.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Use onUnmounted for proper event listener cleanup instead of return function
- Move mouseenter event to tooltip-container to handle disabled button cases
- Remove duplicate CSS definition for .desktop-only class
- Ensure v-if condition is properly applied to mobile-only spacer div
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Display the share button on both desktop and mobile devices
- Add tooltip on desktop showing "Only available on mobile devices"
- Disable button on desktop (non-mobile) devices
- Use position: fixed to avoid parent overflow: hidden issues
- Match existing tooltip design (TryItPackOptions) for consistency
- Support both light and dark modes with #333 background
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Alpine images often omit CA certificates needed for HTTPS git operations. Add ca-certificates to ensure remote cloning/pulls succeed at runtime.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Replace synchronous zlib.inflateSync/deflateSync with async alternatives to prevent blocking the event loop under high load.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add "name": "repomix-website-server" to server/package.json
- Add "name": "repomix-website-client" to client/package.json
- Prevents npm from using /app directory name in package-lock.json during Docker builds
- Ensures consistent package names across development environments
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Update repomix dependency from 0.3.7 to 0.3.9
- Includes latest features and bug fixes
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Optimize resource allocation in cloudbuild.yaml for cost efficiency
- Maintain adequate performance with reduced CPU allocation
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Replace pako.deflate/inflate with zlib.deflateSync/inflateSync in cache.ts
- Remove pako and @types/pako dependencies from package.json
- Utilize Node.js built-in zlib module for better performance and reduced dependencies
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
