Claude-Code-Workflow/.claude/commands/memory/update-related.md

name, description, argument-hint

name	description	argument-hint
update-related	Update CLAUDE.md for git-changed modules using batched agent execution (4 modules/agent) with gemini→qwen→codex fallback, <15 modules uses direct execution	[--tool gemini|qwen|codex]

Related Documentation Update (/memory:update-related)

Overview

Orchestrates context-aware CLAUDE.md updates for changed modules using batched agent execution with automatic tool fallback (gemini→qwen→codex).

Parameters:

• --tool <gemini|qwen|codex>: Primary tool (default: gemini)

Execution Flow:

1. Change Detection → 2. Plan Presentation → 3. Batched Agent Execution → 4. Safety Verification

Core Rules

1. Detect Changes First: Use git diff to identify affected modules
2. Wait for Approval: Present plan, no execution without user confirmation
3. Execution Strategy:
   • <15 modules: Direct parallel execution (max 4 concurrent per depth, no agent overhead)
   • ≥15 modules: Agent batch processing (4 modules/agent, 73% overhead reduction)
4. Tool Fallback: Auto-retry with fallback tools on failure
5. Depth Sequential: Process depths N→0, parallel batches within depth (both modes)
6. Related Mode: Update only changed modules and their parent contexts

Tool Fallback Hierarchy

--tool gemini  →  [gemini, qwen, codex]  // default
--tool qwen    →  [qwen, gemini, codex]
--tool codex   →  [codex, gemini, qwen]

Trigger: Non-zero exit code from update script

Phase 1: Change Detection & Analysis

# Detect changed modules (no index refresh needed)
bash(~/.claude/scripts/detect_changed_modules.sh list)

# Cache git changes
bash(git add -A 2>/dev/null || true)

Parse output depth:N|path:<PATH>|change:<TYPE> to extract affected modules.

Smart filter: Auto-detect and skip tests/build/config/docs based on project tech stack (Node.js/Python/Go/Rust/etc).

Fallback: If no changes detected, use recent modules (first 10 by depth).

Phase 2: Plan Presentation

Present filtered plan:

Related Update Plan:
  Tool: gemini (fallback: qwen → codex)
  Changed: 4 modules | Batching: 4 modules/agent

  Will update:
  - ./src/api/auth (5 files) [new module]
  - ./src/api (12 files) [parent of changed auth/]
  - ./src (8 files) [parent context]
  - . (14 files) [root level]

  Auto-skipped (12 paths):
  - Tests: ./src/api/auth.test.ts (8 paths)
  - Config: tsconfig.json (3 paths)
  - Other: node_modules (1 path)

  Agent allocation:
  - Depth 3 (1 module): 1 agent [1]
  - Depth 2 (1 module): 1 agent [1]
  - Depth 1 (1 module): 1 agent [1]
  - Depth 0 (1 module): 1 agent [1]

  Confirm execution? (y/n)

Decision logic:

• User confirms "y": Proceed with execution
• User declines "n": Abort, no changes
• <15 modules: Direct execution
• ≥15 modules: Agent batch execution

Phase 3A: Direct Execution (<15 modules)

Strategy: Parallel execution within depth (max 4 concurrent), no agent overhead, tool fallback per module.

let modules_by_depth = group_by_depth(changed_modules);
let tool_order = construct_tool_order(primary_tool);

for (let depth of sorted_depths.reverse()) {  // N → 0
  let modules = modules_by_depth[depth];
  let batches = batch_modules(modules, 4);  // Split into groups of 4

  for (let batch of batches) {
    // Execute batch in parallel (max 4 concurrent)
    let parallel_tasks = batch.map(module => {
      return async () => {
        let success = false;
        for (let tool of tool_order) {
          let exit_code = bash(cd ${module.path} && ~/.claude/scripts/update_module_claude.sh "single-layer" "." "${tool}");
          if (exit_code === 0) {
            report("${module.path} updated with ${tool}");
            success = true;
            break;
          }
        }
        if (!success) {
          report("FAILED: ${module.path} failed all tools");
        }
      };
    });

    await Promise.all(parallel_tasks.map(task => task()));  // Run batch in parallel
  }
}

Benefits:

• No agent startup overhead
• Parallel execution within depth (max 4 concurrent)
• Tool fallback still applies per module
• Faster for small changesets (<15 modules)
• Same batching strategy as Phase 3B but without agent layer

---

Phase 3B: Agent Batch Execution (≥15 modules)

Batching Strategy

// Batch modules into groups of 4
function batch_modules(modules, batch_size = 4) {
  let batches = [];
  for (let i = 0; i < modules.length; i += batch_size) {
    batches.push(modules.slice(i, i + batch_size));
  }
  return batches;
}
// Examples: 10→[4,4,2] | 8→[4,4] | 3→[3]

Coordinator Orchestration

let modules_by_depth = group_by_depth(changed_modules);
let tool_order = construct_tool_order(primary_tool);

for (let depth of sorted_depths.reverse()) {  // N → 0
  let batches = batch_modules(modules_by_depth[depth], 4);
  let worker_tasks = [];

  for (let batch of batches) {
    worker_tasks.push(
      Task(
        subagent_type="memory-bridge",
        description=`Update ${batch.length} modules at depth ${depth}`,
        prompt=generate_batch_worker_prompt(batch, tool_order, "related")
      )
    );
  }

  await parallel_execute(worker_tasks);  // Batches run in parallel
}

Batch Worker Prompt Template

PURPOSE: Update CLAUDE.md for assigned modules with tool fallback (related mode)

TASK:
Update documentation for the following modules based on recent changes. For each module, try tools in order until success.

MODULES:
{{module_path_1}}
{{module_path_2}}
{{module_path_3}}
{{module_path_4}}

TOOLS (try in order):
1. {{tool_1}}
2. {{tool_2}}
3. {{tool_3}}

EXECUTION:
For each module above:
  1. cd "{{module_path}}"
  2. Try tool 1:
     bash(cd "{{module_path}}" && ~/.claude/scripts/update_module_claude.sh "single-layer" "." "{{tool_1}}")
     → Success: Report "{{module_path}} updated with {{tool_1}}", proceed to next module
     → Failure: Try tool 2
  3. Try tool 2:
     bash(cd "{{module_path}}" && ~/.claude/scripts/update_module_claude.sh "single-layer" "." "{{tool_2}}")
     → Success: Report "{{module_path}} updated with {{tool_2}}", proceed to next module
     → Failure: Try tool 3
  4. Try tool 3:
     bash(cd "{{module_path}}" && ~/.claude/scripts/update_module_claude.sh "single-layer" "." "{{tool_3}}")
     → Success: Report "{{module_path}} updated with {{tool_3}}", proceed to next module
     → Failure: Report "FAILED: {{module_path}} failed all tools", proceed to next module

REPORTING:
Report final summary with:
- Total processed: X modules
- Successful: Y modules
- Failed: Z modules
- Tool usage: {{tool_1}}:X, {{tool_2}}:Y, {{tool_3}}:Z
- Detailed results for each module

Example Execution

Depth 3 (new module):

Task(subagent_type="memory-bridge", batch=[./src/api/auth], mode="related")

Benefits:

• 4 modules → 1 agent (75% reduction)
• Parallel batches, sequential within batch
• Each module gets full fallback chain
• Context-aware updates based on git changes

Phase 4: Safety Verification

# Check only CLAUDE.md modified
bash(git diff --cached --name-only | grep -v "CLAUDE.md" || echo "Only CLAUDE.md files modified")

# Display statistics
bash(git diff --stat)

Aggregate results:

Update Summary:
  Total: 4 | Success: 4 | Failed: 0

  Tool usage:
  - gemini: 4 modules
  - qwen: 0 modules (fallback)
  - codex: 0 modules

  Changes:
  src/api/auth/CLAUDE.md  | 45 +++++++++++++++++++++
  src/api/CLAUDE.md       | 23 +++++++++--
  src/CLAUDE.md           | 12 ++++--
  CLAUDE.md               | 8 ++--
  4 files changed, 82 insertions(+), 6 deletions(-)

Execution Summary

Module Count Threshold:

• <15 modules: Coordinator executes Phase 3A (Direct Execution)
• ≥15 modules: Coordinator executes Phase 3B (Agent Batch Execution)

Agent Hierarchy (for ≥15 modules):

• Coordinator: Handles batch division, spawns worker agents per depth
• Worker Agents: Each processes 4 modules with tool fallback (related mode)

Error Handling

Batch Worker:

• Tool fallback per module (auto-retry)
• Batch isolation (failures don't propagate)
• Clear per-module status reporting

Coordinator:

• No changes: Use fallback (recent 10 modules)
• User decline: No execution
• Safety check fail: Auto-revert staging
• Partial failures: Continue execution, report failed modules

Fallback Triggers:

• Non-zero exit code
• Script timeout
• Unexpected output

Tool Reference

Tool	Best For	Fallback To
gemini	Documentation, patterns	qwen → codex
qwen	Architecture, system design	gemini → codex
codex	Implementation, code quality	gemini → qwen

Usage Examples

# Daily development update
/memory:update-related

# After feature work with specific tool
/memory:update-related --tool qwen

# Code quality review after implementation
/memory:update-related --tool codex

Key Advantages

Efficiency: 30 modules → 8 agents (73% reduction) Resilience: 3-tier fallback per module Performance: Parallel batches, no concurrency limits Context-aware: Updates based on actual git changes Fast: Only affected modules, not entire project

Coordinator Checklist

• Parse --tool (default: gemini)
• Refresh code index for accurate change detection
• Detect changed modules via detect_changed_modules.sh
• Smart filter modules (auto-detect tech stack, skip tests/build/config/docs)
• Cache git changes
• Apply fallback if no changes (recent 10 modules)
• Construct tool fallback order
• Present filtered plan with skip reasons and change types
• Wait for y/n confirmation
• Determine execution mode:
  • <15 modules: Direct execution (Phase 3A)
    • For each depth (N→0): Sequential module updates with tool fallback
  • ≥15 modules: Agent batch execution (Phase 3B)
    • For each depth (N→0): Batch modules (4 per batch), spawn batch workers in parallel
• Wait for depth/batch completion
• Aggregate results
• Safety check (only CLAUDE.md modified)
• Display git diff statistics + summary

Comparison with Full Update

Aspect	Related Update	Full Update
Scope	Changed modules only	All project modules
Speed	Fast (minutes)	Slower (10-30 min)
Use case	Daily development	Major refactoring
Mode	"related"	"full"
Trigger	After commits	After major changes
Batching	4 modules/agent	4 modules/agent
Fallback	gemini→qwen→codex	gemini→qwen→codex
Complexity threshold	≤15 modules	≤20 modules