docs: add bash execution rules and Windows path conversion guide

- Add rule to prevent run_in_background parameter in bash() calls
- Add Windows path conversion guidelines for Git Bash compatibility
- Simplify path handling: C:\path → /c/path, relative paths unchanged
This commit is contained in:
catlog22
2025-10-12 17:19:47 +08:00
parent 8e4710389d
commit 9d4d728ee7
3 changed files with 7 additions and 0 deletions

View File

@@ -36,6 +36,7 @@ argument-hint: "[--tool gemini|qwen|codex] [--path <directory>]"
4. **Depth-Parallel**: Same depth runs parallel (max 4 jobs), different depths sequential
5. **Safety Check**: Verify only CLAUDE.md files modified, revert if source files touched
6. **Independent Commands**: Each update is a separate bash() call
7. **No Background Bash Tool**: Never use `run_in_background` parameter in bash() calls; use shell `&` for parallelism
## Execution Workflow

View File

@@ -30,6 +30,7 @@ argument-hint: "[--tool gemini|qwen|codex]"
3. **Related Mode**: Update only changed modules and their parent contexts
4. **Depth-Parallel**: Same depth runs parallel (max 4 jobs), different depths sequential
5. **Safety Check**: Verify only CLAUDE.md files modified, revert if source files touched
6. **No Background Bash Tool**: Never use `run_in_background` parameter in bash() calls; use shell `&` for parallelism
## Execution Workflow

View File

@@ -70,6 +70,11 @@ For all CLI tool usage, command syntax, and integration guidelines:
- Learn from existing implementations
- Stop after 3 failed attempts and reassess
## Platform-Specific Guidelines
### Windows Path Conversion for Bash Commands
- **Windows paths** must convert to Git Bash format: `C:\path``/c/path`, `D:\path``/d/path`, `\``/`
- **Relative paths** (starting with `.` or `..`) require no conversion
#### **Content Uniqueness Rules**