mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-10 02:24:35 +08:00
docs: remove direct Gemini Wrapper script usage section
Removed the "Direct Gemini Wrapper Script Usage" section from Getting Started guides as users cannot manually execute these commands in Claude Code - all tool invocations are handled automatically by Claude through semantic understanding. Changes: - Removed "Gemini Wrapper 脚本直接使用" section (Chinese) - Removed "Direct Gemini Wrapper Script Usage" section (English) - Kept "Semantic Tool Invocation" section explaining natural language usage - Streamlined documentation to focus on user-facing interaction patterns Rationale: - Users cannot run ~/.claude/scripts/gemini-wrapper commands directly in Claude Code - These are internal implementation details handled automatically by Claude - Documentation should focus on how users interact with the system, not internal mechanics Files updated: - GETTING_STARTED.md (-47 lines) - GETTING_STARTED_CN.md (-47 lines) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -201,56 +201,6 @@ User: "Use codex to implement user login functionality"
|
||||
- **Intelligent Understanding**: Claude selects appropriate tools and parameters based on context
|
||||
- **Automatic Optimization**: Claude automatically adds necessary context and configuration
|
||||
|
||||
### Direct Gemini Wrapper Script Usage
|
||||
|
||||
For scenarios requiring precise control, the Gemini Wrapper script can be used directly.
|
||||
|
||||
#### Basic Analysis (Read-only Mode)
|
||||
|
||||
By default, Gemini runs in read-only mode, suitable for code exploration and architectural analysis:
|
||||
|
||||
```bash
|
||||
# Execute analysis in project root
|
||||
cd /path/to/project && ~/.claude/scripts/gemini-wrapper -p "
|
||||
PURPOSE: Analyze project modular architecture
|
||||
TASK: Identify core modules and their dependencies
|
||||
CONTEXT: @{src/**/*.ts,CLAUDE.md}
|
||||
EXPECTED: Generate architecture diagram and module documentation
|
||||
RULES: Focus on module boundaries and interface design
|
||||
"
|
||||
```
|
||||
|
||||
#### Document Generation (Write Mode)
|
||||
|
||||
When file generation or modification is needed, write mode must be explicitly enabled:
|
||||
|
||||
```bash
|
||||
# Generate API documentation
|
||||
cd /path/to/project && ~/.claude/scripts/gemini-wrapper --approval-mode yolo -p "
|
||||
PURPOSE: Generate REST API documentation
|
||||
TASK: Extract API endpoints from code and generate Markdown docs
|
||||
MODE: write
|
||||
CONTEXT: @{src/api/**/*.ts}
|
||||
EXPECTED: Generate API.md with all endpoint descriptions
|
||||
RULES: Follow OpenAPI specification format
|
||||
"
|
||||
```
|
||||
|
||||
#### Context Optimization Techniques
|
||||
|
||||
Using `cd` to switch to specific directories optimizes context scope:
|
||||
|
||||
```bash
|
||||
# Analyze only auth module
|
||||
cd src/auth && ~/.claude/scripts/gemini-wrapper -p "
|
||||
PURPOSE: Security review of authentication module
|
||||
TASK: Check JWT implementation and password handling
|
||||
CONTEXT: @{**/*.ts}
|
||||
EXPECTED: Security audit report
|
||||
RULES: Focus on OWASP Top 10 security issues
|
||||
"
|
||||
```
|
||||
|
||||
### Memory Management: CLAUDE.md Updates
|
||||
|
||||
CCW uses a hierarchical CLAUDE.md documentation system to maintain project context. Regular updates to these documents are critical for ensuring high-quality AI outputs.
|
||||
|
||||
Reference in New Issue
Block a user