claude_code
Execute code, file, Git, and terminal tasks with a multi-modal assistant. Manage workflows, refactor code, and integrate with GitHub using natural language prompts for streamlined development.
Instructions
Claude Code Agent: Your versatile multi-modal assistant for code, file, Git, and terminal operations via Claude CLI. Use workFolder for contextual execution.
• File ops: Create, read, (fuzzy) edit, move, copy, delete, list files, analyze/ocr images, file content analysis └─ e.g., "Create /tmp/log.txt with 'system boot'", "Edit main.py to replace 'debug_mode = True' with 'debug_mode = False'", "List files in /src", "Move a specific section somewhere else"
• Code: Generate / analyse / refactor / fix └─ e.g. "Generate Python to parse CSV→JSON", "Find bugs in my_script.py"
• Git: Stage ▸ commit ▸ push ▸ tag (any workflow) └─ "Commit '/workspace/src/main.java' with 'feat: user auth' to develop."
• Terminal: Run any CLI cmd or open URLs └─ "npm run build", "Open https://developer.mozilla.org"
• Web search + summarise content on-the-fly
• Multi-step workflows (Version bumps, changelog updates, release tagging, etc.)
• GitHub integration Create PRs, check CI status
• Confused or stuck on an issue? Ask Claude Code for a second opinion, it might surprise you!
• Task Orchestration with "Boomerang" pattern └─ Break down complex tasks into subtasks for Claude Code to execute separately └─ Pass parent task ID and get results back for complex workflows └─ Specify return mode (summary or full) for tailored responses
Prompt tips
Be concise, explicit & step-by-step for complex tasks. No need for niceties, this is a tool to get things done.
For multi-line text, write it to a temporary file in the project root, use that file, then delete it.
If you get a timeout, split the task into smaller steps.
Seeking a second opinion/analysis: If you're stuck or want advice, you can ask
claude_codeto analyze a problem and suggest solutions. Clearly state in your prompt that you are looking for analysis only and no actual file modifications should be made.If workFolder is set to the project path, there is no need to repeat that path in the prompt and you can use relative paths for files.
Claude Code is really good at complex multi-step file operations and refactorings and faster than your native edit features.
Combine file operations, README updates, and Git commands in a sequence.
Task Orchestration: For complex workflows, use
parentTaskIdto create subtasks andreturnMode: "summary"to get concise results back.Claude can do much more, just ask it!
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | When MCP_USE_ROOMODES=true, specifies the mode from .roomodes to use (e.g., "boomerang-mode", "coder", "designer", etc.). | |
| parentTaskId | No | Optional ID of the parent task that created this task (for task orchestration/boomerang). | |
| prompt | Yes | The detailed natural language prompt for Claude to execute. | |
| returnMode | No | How results should be returned: summary (concise) or full (detailed). Defaults to full. | |
| taskDescription | No | Short description of the task for better organization and tracking in orchestrated workflows. | |
| workFolder | No | Mandatory when using file operations or referencing any file. The working directory for the Claude CLI execution. |