refactor: rename memory-gemini-bridge agent to memory-bridge

Renamed agent to be more generic and not tied to specific AI model:
- `.claude/agents/memory-gemini-bridge.md` → `.claude/agents/memory-bridge.md`
- Updated references in `/update-memory-full` command
- Updated references in `/update-memory-related` command

This improves flexibility for future multi-model support while maintaining
the same functionality for complex project documentation updates.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
catlog22
2025-10-05 21:25:59 +08:00
parent 2dbf550420
commit 677b37bfbf
3 changed files with 9 additions and 9 deletions

View File

@@ -1,5 +1,5 @@
---
name: memory-gemini-bridge
name: memory-bridge
description: Execute complex project documentation updates using script coordination
color: purple
---

View File

@@ -45,7 +45,7 @@ count=$(echo "$modules" | wc -l)
# Pseudocode flow:
# IF (module_count > 20 OR complex_project_detected):
# → Task "Complex project full update" subagent_type: "memory-gemini-bridge"
# → Task "Complex project full update" subagent_type: "memory-bridge"
# ELSE:
# → Present plan and WAIT FOR USER APPROVAL before execution
#
@@ -60,7 +60,7 @@ After the bash script completes the initial analysis, the model takes control to
2. **Parse CLAUDE.md Status**: Extract which modules have/need CLAUDE.md files
3. **Choose Strategy**:
- Simple projects: Present execution plan with CLAUDE.md paths to user
- Complex projects: Delegate to memory-gemini-bridge agent
- Complex projects: Delegate to memory-bridge agent
4. **Present Detailed Plan**: Show user exactly which CLAUDE.md files will be created/updated
5. **⚠️ CRITICAL: WAIT FOR USER APPROVAL**: No execution without explicit user consent
@@ -120,11 +120,11 @@ Bash(git status --short)
**For Complex Projects (>20 modules):**
The model will delegate to the memory-gemini-bridge agent with structured context:
The model will delegate to the memory-bridge agent with structured context:
```javascript
Task "Complex project full update"
subagent_type: "memory-gemini-bridge"
subagent_type: "memory-bridge"
prompt: `
CONTEXT:
- Total modules: ${module_count}

View File

@@ -51,7 +51,7 @@ count=$(echo "$changed" | wc -l)
# Pseudocode flow:
# IF (change_count > 15 OR complex_changes_detected):
# → Task "Complex project related update" subagent_type: "memory-gemini-bridge"
# → Task "Complex project related update" subagent_type: "memory-bridge"
# ELSE:
# → Present plan and WAIT FOR USER APPROVAL before execution
#
@@ -66,7 +66,7 @@ After the bash script completes change detection, the model takes control to:
2. **Parse CLAUDE.md Status**: Extract which changed modules have/need CLAUDE.md files
3. **Choose Strategy**:
- Simple changes: Present execution plan with CLAUDE.md paths to user
- Complex changes: Delegate to memory-gemini-bridge agent
- Complex changes: Delegate to memory-bridge agent
4. **Present Detailed Plan**: Show user exactly which CLAUDE.md files will be created/updated for changed modules
5. **⚠️ CRITICAL: WAIT FOR USER APPROVAL**: No execution without explicit user consent
@@ -127,11 +127,11 @@ Bash(git diff --stat)
**For Complex Changes (>15 modules):**
The model will delegate to the memory-gemini-bridge agent with structured context:
The model will delegate to the memory-bridge agent with structured context:
```javascript
Task "Complex project related update"
subagent_type: "memory-gemini-bridge"
subagent_type: "memory-bridge"
prompt: `
CONTEXT:
- Total modules: ${change_count}