Files
Claude-Code-Workflow/.claude/commands/codex/analyze.md
catlog22 1357756295 refactor: Update all codex commands to use -s danger-full-access and correct syntax
- Move -s parameter to end of command: codex --full-auto exec "..." -s danger-full-access
- Change default sandbox mode from workspace-write to danger-full-access
- Add missing --full-auto parameter to commands requiring autonomous development
- Add missing exec parameter to all codex commands
- Add missing -s danger-full-access parameter to multi-line commands
- Update all documentation and examples to use consistent syntax
- Fix CLAUDE.md detection functionality in detect_changed_modules.sh script

Files updated:
- Core configuration: CLAUDE.md, RELEASE_NOTES_v1.3.0.md
- Documentation: tools-implementation-guide.md, intelligent-tools-strategy.md
- Command files: All .claude/commands/codex/*.md and workflow/*.md files
- Agent templates: action-planning-agent.md
- Scripts: detect_changed_modules.sh

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

Co-Authored-By: Claude <noreply@anthropic.com>
2025-09-16 13:11:13 +08:00

5.4 KiB

name, description, usage, argument-hint, examples, model
name description usage argument-hint examples model
analyze Quick analysis of codebase patterns, architecture, and code quality using Codex CLI /codex:analyze <analysis-type> analysis target or type
/codex:analyze "React hooks patterns"
/codex:analyze "authentication security"
/codex:analyze "performance bottlenecks"
/codex:analyze "API design patterns"
haiku

Codex Analysis Command (/codex:analyze)

Overview

Quick analysis tool for codebase insights using intelligent pattern detection and template-driven analysis with Codex CLI.

Core Guidelines: @~/.claude/workflows/tools-implementation-guide.md

⚠️ Critical Difference: Codex has NO --all-files flag - you MUST use @ patterns to reference files.

Analysis Types

Type Purpose Example
pattern Code pattern detection "React hooks usage patterns"
architecture System structure analysis "component hierarchy structure"
security Security vulnerabilities "authentication vulnerabilities"
performance Performance bottlenecks "rendering performance issues"
quality Code quality assessment "testing coverage analysis"
dependencies Third-party analysis "outdated package dependencies"

Quick Usage

Basic Analysis

/codex:analyze "authentication patterns"

Executes: codex --full-auto exec "@{**/*auth*} @{CLAUDE.md} $(cat ~/.claude/workflows/cli-templates/prompts/analysis/pattern.txt)" -s danger-full-access

Targeted Analysis

/codex:analyze "React component architecture"

Executes: codex --full-auto exec "@{src/components/**/*} @{CLAUDE.md} $(cat ~/.claude/workflows/cli-templates/prompts/analysis/architecture.txt)" -s danger-full-access

Security Focus

/codex:analyze "API security vulnerabilities"

Executes: codex --full-auto exec "@{**/api/**/*} @{CLAUDE.md} $(cat ~/.claude/workflows/cli-templates/prompts/analysis/security.txt)" -s danger-full-access

Codex-Specific Patterns

Essential File Patterns (Required for Codex):

@{**/*}                    # All files recursively
@{src/**/*}               # All source files
@{*.ts,*.js}              # Specific file types
@{CLAUDE.md,**/*CLAUDE.md} # Documentation hierarchy
@{package.json,*.config.*} # Configuration files

Templates Used

Templates are automatically selected based on analysis type:

  • Pattern Analysis: ~/.claude/workflows/cli-templates/prompts/analysis/pattern.txt
  • Architecture Analysis: ~/.claude/workflows/cli-templates/prompts/analysis/architecture.txt
  • Security Analysis: ~/.claude/workflows/cli-templates/prompts/analysis/security.txt
  • Performance Analysis: ~/.claude/workflows/cli-templates/prompts/analysis/performance.txt

Workflow Integration

⚠️ Session Check: Automatically detects active workflow session via .workflow/.active-* marker file.

Analysis results saved to:

  • Active session: .workflow/WFS-[topic]/.chat/analysis-[timestamp].md
  • No session: Temporary analysis output

Common Patterns

Technology Stack Analysis

/codex:analyze "project technology stack"
# Executes: codex --full-auto exec "@{package.json,*.config.*,CLAUDE.md} [analysis prompt]" -s danger-full-access

Code Quality Review

/codex:analyze "code quality and standards"
# Executes: codex --full-auto exec "@{src/**/*,test/**/*,CLAUDE.md} [analysis prompt]" -s danger-full-access

Migration Planning

/codex:analyze "legacy code modernization"
# Executes: codex --full-auto exec "@{**/*.{js,jsx,ts,tsx},CLAUDE.md} [analysis prompt]" -s danger-full-access

Module-Specific Analysis

/codex:analyze "authentication module patterns"
# Executes: codex --full-auto exec "@{src/auth/**/*,**/*auth*,CLAUDE.md} [analysis prompt]" -s danger-full-access

Output Format

Analysis results include:

  • File References: Specific file:line locations
  • Code Examples: Relevant code snippets
  • Patterns Found: Common patterns and anti-patterns
  • Recommendations: Actionable improvements
  • Integration Points: How components connect

Execution Templates

Basic Analysis Template

codex --full-auto exec "@{inferred_patterns} @{CLAUDE.md,**/*CLAUDE.md}

Analysis Type: [analysis_type]

Provide:
- Pattern identification and analysis
- Code quality assessment
- Architecture insights
- Specific recommendations with file:line references" -s danger-full-access

Template-Enhanced Analysis

codex --full-auto exec "@{inferred_patterns} @{CLAUDE.md,**/*CLAUDE.md} $(cat ~/.claude/workflows/cli-templates/prompts/analysis/[template].txt)

Focus: [analysis_type]
Context: [user_description]" -s danger-full-access

Error Prevention

  • Always include @ patterns: Commands without file references will fail
  • Test patterns first: Validate @ patterns match existing files
  • Use comprehensive patterns: @{**/*} when unsure of file structure
  • Include documentation: Always add @{CLAUDE.md,**/*CLAUDE.md} for context

Codex vs Gemini

Feature Codex Gemini
File Loading @ patterns required --all-files available
Command Structure codex exec "@{patterns}" gemini --all-files -p
Pattern Flexibility Must be explicit Auto-includes with flag

For detailed syntax, patterns, and advanced usage see: @~/.claude/workflows/tools-implementation-guide.md