mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-14 02:42:04 +08:00
## New Features - **Dual-mode update-memory commands**: /update-memory-full and /update-memory-related - **Git-aware change detection**: Intelligent context-aware documentation updates - **Complexity-adaptive execution**: Auto-delegation to memory-gemini-bridge for complex projects - **Depth-parallel processing**: Bottom-up execution ensuring proper context propagation - **Enhanced issue tracking integration**: Complete /workflow:issue:* command set documentation ## New Scripts & Infrastructure - detect_changed_modules.sh: Git-based change detection with fallback strategies - get_modules_by_depth.sh: Hierarchical module discovery and organization - update_module_claude.sh: Core CLAUDE.md update execution engine ## Documentation Updates - **README.md**: Added comprehensive update-memory system documentation with usage examples - **README_CN.md**: Complete Chinese localization of new features and technical details - **Command reference tables**: Updated with new /update-memory-* commands and /workflow:issue:* set - **Technical highlights**: Enhanced with dual-mode operations and complexity thresholds - **Usage workflows**: Added detailed examples for different development scenarios ## Technical Improvements - Streamlined memory-gemini-bridge.md (reduced by 200+ lines) - Simplified gemini-unified.md workflow documentation - Added comprehensive CLAUDE.md files for new modules - Enhanced DMS (Distributed Memory System) with 4-layer hierarchy templates ## Architecture Enhancements - **Complexity thresholds**: related mode (>15 modules), full mode (>20 modules) - **Git integration**: Smart change detection with comprehensive status reporting - **User confirmation workflows**: Clear execution plans with mandatory approval steps - **Fallback strategies**: Graceful handling of non-git environments 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
69 lines
2.1 KiB
Plaintext
69 lines
2.1 KiB
Plaintext
Create or update sub-module-level CLAUDE.md documentation:
|
|
|
|
## Layer 4: Sub-Module Level Documentation Requirements
|
|
|
|
### Content Focus (MUST INCLUDE):
|
|
1. **Detailed Implementation Specifics**
|
|
- Specific implementation details and algorithms
|
|
- Code-level patterns and idioms
|
|
- Implementation trade-offs and decisions
|
|
|
|
2. **Component/Function Documentation**
|
|
- Individual component descriptions
|
|
- Function signatures and behaviors
|
|
- Class/struct/interface documentation
|
|
|
|
3. **Configuration Details and Examples**
|
|
- Configuration options and parameters
|
|
- Environment-specific settings
|
|
- Configuration examples and templates
|
|
|
|
4. **Usage Examples and Patterns**
|
|
- Code examples and usage patterns
|
|
- Common use cases and scenarios
|
|
- Integration examples with other components
|
|
|
|
5. **Performance Considerations**
|
|
- Performance characteristics and constraints
|
|
- Optimization strategies and techniques
|
|
- Resource usage and scalability notes
|
|
|
|
### Content Restrictions (STRICTLY AVOID):
|
|
- Architecture decisions (belong in higher levels)
|
|
- Module-level organizational patterns (belong in module-level docs)
|
|
- Domain or project overview content (belong in higher levels)
|
|
- Cross-module architectural concerns (belong in higher levels)
|
|
|
|
### Documentation Style:
|
|
- Focus on detailed, actionable implementation information
|
|
- Provide concrete examples and code snippets
|
|
- Document specific behaviors and edge cases
|
|
- Include troubleshooting and debugging guidance
|
|
|
|
### Template Structure:
|
|
```markdown
|
|
# [Sub-Module/Component Name] - Implementation Guide
|
|
|
|
## 1. Component Overview
|
|
[Specific purpose and functionality]
|
|
|
|
## 2. Implementation Details
|
|
[Detailed implementation specifics]
|
|
|
|
## 3. API Reference
|
|
[Function/method documentation]
|
|
|
|
## 4. Configuration
|
|
[Configuration options and examples]
|
|
|
|
## 5. Usage Examples
|
|
[Code examples and patterns]
|
|
|
|
## 6. Performance and Optimization
|
|
[Performance considerations and tips]
|
|
|
|
## 7. Troubleshooting
|
|
[Common issues and solutions]
|
|
```
|
|
|
|
Remember: This is Layer 4 - focus on concrete, actionable implementation details and avoid architectural or organizational concerns. |