mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-12 02:37:45 +08:00
feat: Add Codex analysis step with directory context to workflow plan
- Add optional analyze_implementation step using Codex CLI tool - Include -C parameter for directory-focused development analysis - Enhance pre_analysis flow with both Gemini and Codex options - Improve agent context loading with implementation-focused patterns 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -105,10 +105,17 @@ The following pre_analysis steps are generated for agent execution:
|
|||||||
},
|
},
|
||||||
{
|
{
|
||||||
"step": "analyze_patterns",
|
"step": "analyze_patterns",
|
||||||
"action": "Analyze codebase patterns and architecture using CLI tools",
|
"action": "Analyze codebase patterns and architecture using CLI tools with directory context",
|
||||||
"command": "bash(~/.claude/scripts/gemini-wrapper -p \"PURPOSE: Analyze existing patterns TASK: Identify implementation patterns for [task_type] CONTEXT: [planning_context] [dependency_context] EXPECTED: Pattern analysis and recommendations RULES: Focus on architectural consistency\")",
|
"command": "bash(~/.claude/scripts/gemini-wrapper -C [target_directory] -p \"PURPOSE: Analyze existing patterns TASK: Identify implementation patterns for [task_type] CONTEXT: [planning_context] [dependency_context] EXPECTED: Pattern analysis and recommendations RULES: Focus on architectural consistency\")",
|
||||||
"output_to": "pattern_analysis",
|
"output_to": "pattern_analysis",
|
||||||
"on_error": "skip_optional"
|
"on_error": "skip_optional"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"step": "analyze_implementation",
|
||||||
|
"action": "Development-focused analysis using Codex when needed",
|
||||||
|
"command": "bash(codex -C [target_directory] --full-auto exec \"PURPOSE: Analyze implementation patterns TASK: Review development patterns for [task_type] CONTEXT: [planning_context] [dependency_context] EXPECTED: Development strategy and code patterns RULES: Focus on implementation consistency\" -s danger-full-access)",
|
||||||
|
"output_to": "implementation_analysis",
|
||||||
|
"on_error": "skip_optional"
|
||||||
}
|
}
|
||||||
]
|
]
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user