37 lines
1.3 KiB
Markdown
37 lines
1.3 KiB
Markdown
|
# Start Migration from Claude Code
|
||
|
|
|
||
|
|
The agent scripts need to be launched **from within Claude Code** using the Task tool, not from command line.
|
||
|
|
|
||
|
|
## How to Launch Agents
|
||
|
|
|
||
|
|
### Option 1: Ask Claude Code to Run Migration
|
||
|
|
```
|
||
|
|
Hey Claude, please run the config-driven migration using the agent scripts in .migration/agents/
|
||
|
|
```
|
||
|
|
|
||
|
|
### Option 2: Launch Individual Agents
|
||
|
|
```
|
||
|
|
Claude, please launch the syntax analyzer agent using the instructions in .migration/agents/01_analyze_syntax.sh
|
||
|
|
```
|
||
|
|
|
||
|
|
### Option 3: Use Task Tool Directly (if in Claude Code session)
|
||
|
|
```nushell
|
||
|
|
# Example of how Claude Code would launch an agent:
|
||
|
|
Task "syntax-analyzer" "Find syntax errors using .migration/knowledge/SYNTAX_FIX_CARD.md" "general-purpose"
|
||
|
|
```
|
||
|
|
|
||
|
|
## Why Command Line Doesn't Work
|
||
|
|
|
||
|
|
The `claude-code` command in the scripts was a placeholder. Claude Code agents must be launched from **within a Claude Code session** using the Task tool.
|
||
|
|
|
||
|
|
## Alternative: Manual Migration
|
||
|
|
|
||
|
|
If you want to run without agents, you can manually:
|
||
|
|
|
||
|
|
1. **Find syntax errors**: `find core/ -name "*.nu" -exec nu --ide-check {} \;`
|
||
|
|
2. **Find ENV references**: `grep -r "\$env.PROVISIONING" core/`
|
||
|
|
3. **Fix manually** using patterns in `.migration/knowledge/`
|
||
|
|
|
||
|
|
## Recommended Approach
|
||
|
|
|
||
|
|
**Ask Claude Code to run the migration** - it can launch the agents properly using the Task tool and coordinate the entire process.
|