docs: Distinguish command syntax differences between Gemini and Codex tools

- Add critical warnings in codex-unified.md that no wrapper script exists
- Clarify in intelligent-tools.md that Gemini has wrapper, Codex uses direct commands
- Prevent confusion about non-existent ~/.claude/scripts/codex
- Emphasize correct usage: gemini-wrapper vs codex --full-auto exec
- Clean up CLAUDE.md tool references for consistency

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

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
catlog22
2025-09-14 20:41:05 +08:00
parent 845925dffb
commit 62f05827a1
3 changed files with 21 additions and 4 deletions

View File

@@ -4,9 +4,10 @@ description: Comprehensive Codex CLI guidelines - core rules, syntax, patterns,
type: technical-guideline
---
### 🚀 Command Overview: Bash(codex *)
### 🚀 Command Overview: Bash(codex *)
- **Purpose**: An AI-powered CLI tool for automated codebase analysis, intelligent code generation, and autonomous development workflows.
- **⚠️ CRITICAL**: **NO wrapper script exists** - always use direct `codex` command, never `~/.claude/scripts/codex`
- **Key Characteristic**: **No `--all-files` flag** - requires explicit `@` pattern references for file inclusion.
- **Directory Analysis Rule**: When user intends to analyze specific directory (cd XXX), use: `bash(codex --cd XXX --full-auto exec "prompt")` or `bash(cd XXX && codex --full-auto exec "@{**/*} prompt")`
- **Default Mode**: `--full-auto exec` autonomous development mode (RECOMMENDED for all tasks).
@@ -42,8 +43,10 @@ type: technical-guideline
- **Basic Structure** (Priority Order):
```bash
bash(codex --full-auto exec "autonomous development task") # DEFAULT & RECOMMENDED
bash(codex --full-auto exec "prompt with @{patterns}") # For specific control needs
bash(codex --full-auto exec "prompt with @{patterns}") # For specific control needs
```
**⚠️ NEVER use**: `~/.claude/scripts/codex` - this wrapper script does not exist!
- **Key Commands** (In Order of Preference):
- `bash(codex --full-auto exec "...")` ⭐ **PRIMARY MODE** - Full autonomous development
- `bash(codex --full-auto exec "...")` - Controlled execution when you need specific patterns

View File

@@ -16,6 +16,7 @@ This document provides strategic guidance for selecting the appropriate analysis
## Tool Characteristics Comparison
### Gemini
- **Command Syntax**: `bash(~/.claude/scripts/gemini-wrapper -p "prompt")` (HAS wrapper script)
- **Strengths**:
- Large context window for analyzing many files simultaneously
- Excellent pattern recognition across modules
@@ -27,6 +28,7 @@ This document provides strategic guidance for selecting the appropriate analysis
- Refactoring with broad dependencies
### Codex
- **Command Syntax**: `bash(codex --full-auto exec "prompt")` (NO wrapper script - direct command only)
- **Strengths**:
- Superior mathematical and algorithmic reasoning
- Deeper technical knowledge base
@@ -82,6 +84,20 @@ Task(subagent_type="general-purpose",
Commands should reference this strategy guide for tool selection decisions.
Specific tool usage syntax and examples are documented in their respective unified guides.
## ⚠️ CRITICAL Command Syntax Differences
**Gemini** (HAS intelligent wrapper):
```bash
bash(~/.claude/scripts/gemini-wrapper -p "analyze patterns")
```
**Codex** (NO wrapper - direct command only):
```bash
bash(codex --full-auto exec "implement feature")
```
**❌ NEVER use**: `~/.claude/scripts/codex` - this does not exist!
**See also**:
- Gemini detailed usage: @~/.claude/workflows/gemini-unified.md
- Codex detailed usage: @~/.claude/workflows/codex-unified.md

View File

@@ -5,8 +5,6 @@
This document defines project-specific coding standards and development principles.
### CLI Tool Context Protocols
For all CLI tool usage, command syntax, and integration guidelines:
- **Gemini (Analysis)**: @~/.claude/workflows/gemini-unified.md
- **Codex (Development)**: @~/.claude/workflows/codex-unified.md
- **Tool Selection Strategy**: @~/.claude/workflows/intelligent-tools.md
### Intelligent Context Acquisition