mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-13 02:41:50 +08:00
46911ec251
## Command Updates - Renamed `/update_dms` → `/update-memory` for kebab-case consistency - Updated all references across documentation, installation scripts, and agents ## Files Updated - `.claude/commands/update_dms.md` → `.claude/commands/update-memory.md` - Updated 8 files with command name references - Updated both English and Chinese README files - Updated installation scripts and agent documentation ## Documentation Enhancement - Added comprehensive command streamlining section to CHANGELOG.md - Documented removal of 4 redundant commands (context.md, sync.md) - Documented cleanup of 10 legacy documentation files - Highlighted 60% reduction in maintenance overhead ## Consistency Improvements - Standardized command naming convention across entire system - Enhanced session management documentation - Improved error handling documentation for session registry 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
72 lines
3.0 KiB
Markdown
72 lines
3.0 KiB
Markdown
# Gemini Memory-Gemini-Bridge Template
|
|
|
|
**Purpose**: Comprehensive project structure analysis for hierarchical CLAUDE.md documentation generation
|
|
|
|
## Template Structure
|
|
|
|
```bash
|
|
gemini --all-files -p "@{**/*} @{CLAUDE.md,**/*CLAUDE.md} @{package*.json,requirements.txt,pom.xml,Cargo.toml}
|
|
|
|
Project structure analysis for Memory-Gemini-Bridge documentation generation:
|
|
Target: [project-name or specific scope]
|
|
|
|
## Required Analysis:
|
|
1. **Project Architecture Assessment**:
|
|
- Overall system structure and module organization
|
|
- Technology stack diversity and integration complexity
|
|
- Existing CLAUDE.md hierarchy and content gaps
|
|
- Directory structure patterns and logical groupings
|
|
|
|
2. **Documentation Hierarchy Strategy**:
|
|
- Identify optimal CLAUDE.md placement levels (root, module, sub-module)
|
|
- Determine content differentiation across hierarchy levels
|
|
- Assess complexity thresholds for documentation depth
|
|
- Map existing documentation patterns and standards
|
|
|
|
3. **Cross-System Integration Analysis**:
|
|
- Claude-Gemini compatibility requirements
|
|
- Cross-system documentation synchronization patterns
|
|
- Template and guideline reference patterns
|
|
- Memory system synchronization needs
|
|
|
|
4. **Module Responsibility Mapping**:
|
|
- Core module identification and purpose analysis
|
|
- Inter-module dependencies and integration patterns
|
|
- Component organization and architectural boundaries
|
|
- Implementation pattern consistency across modules
|
|
|
|
5. **Technology Stack Integration**:
|
|
- Framework usage patterns and configuration analysis
|
|
- Build system and development workflow patterns
|
|
- Testing architecture and quality standards
|
|
- Deployment and infrastructure considerations
|
|
|
|
## Output Requirements:
|
|
- **Hierarchy Recommendation**: Specific CLAUDE.md file structure with rationale
|
|
- **Content Strategy**: Level-specific focus areas and content differentiation
|
|
- **Template Selection**: Appropriate DMS and core templates for analysis
|
|
- **Integration Plan**: Workflow coordination with update-memory and agent systems
|
|
- **Quality Standards**: Cross-system compatibility and maintenance guidelines
|
|
|
|
Focus on architectural understanding for documentation strategy rather than implementation details."
|
|
```
|
|
|
|
## Context Application
|
|
|
|
- Generate hierarchical documentation strategy based on project structure
|
|
- Create comprehensive CLAUDE.md files with appropriate content depth
|
|
- Ensure cross-system compatibility between Claude and Gemini CLI
|
|
- Establish maintainable documentation patterns for ongoing development
|
|
|
|
## Usage Guidelines
|
|
|
|
**Use Memory-Gemini-Bridge template when**:
|
|
- Creating or updating CLAUDE.md files for Gemini CLI compatibility
|
|
- Establishing hierarchical documentation strategy for complex projects
|
|
- Synchronizing memory systems between Claude and Gemini CLI
|
|
|
|
**Template focuses on**:
|
|
- Comprehensive project structure analysis
|
|
- Documentation hierarchy strategy and content differentiation
|
|
- Cross-system integration analysis for Claude-Gemini compatibility
|
|
- Architectural understanding for documentation strategy rather than implementation details |