1270011/claude-buddy/buddy

Buddy — Your Coding Companion

Handle the user's /buddy command using the coding-buddy MCP tools.

Fallback: MCP Tools Unavailable

Before routing any command, check whether `mcp__claude_buddy__*` tools are registered in this session. If they are NOT — Claude Code was unable to start the coding-buddy MCP server — do not attempt to call any buddy tool. The tool calls will fail with an unhelpful "tool not found" error. Instead, run this diagnostic and report the result to the user so they can fix the underlying cause:

1. Check bun availability:

``bash command -v bun && bun --version ` The MCP launcher (server/mcp-launcher.sh) requires bun on PATH. If this command prints nothing, bun is missing — tell the user to install it (curl -fsSL https://bun.sh/install | bash`), open a new terminal so PATH picks it up, and restart Claude Code. That is almost always the fix.

1. If bun IS present, run the launcher directly to capture whatever error it emits. The launcher path depends on which marketplace installed the plugin; locate it first:

``bash find ~/.claude/plugins/cache -name mcp-launcher.sh -path '*coding-buddy*' 2>/dev/null ` Then execute the first result with stdin closed so it exits cleanly: `bash <launcher-path> < /dev/null; echo "exit=$?" ` Common causes: missing bun, corrupted plugin cache (suggest claude plugin uninstall coding-buddy@coding-buddy && claude plugin install coding-buddy@coding-buddy), or a bun-level error loading server/index.ts`.

1. If $CLAUDE_CONFIG_DIR is set in the environment, use that directory instead of ~/.claude when searching for the launcher.

1. Do not proceed with any buddy command in this session. Tell the user: the MCP server is not running, here is what the diagnostic found, here is the recommended fix, and Claude Code must be restarted after the fix before buddy tools will be available.

Command Routing

Based on $ARGUMENTS:

CRITICAL OUTPUT RULES

The MCP tools return pre-formatted ASCII art with ANSI colors, box-drawing characters, stat bars, and species art. This is the companion's visual identity.

You MUST output the tool result text EXACTLY as returned — character for character, line for line. Do NOT:

• Summarize or paraphrase the ASCII art
• Describe what the companion looks like in prose
• Add commentary before or after the card
• Reformat, rephrase, or interpret the output
• Strip ANSI escape codes

Just output the raw text content from the tool result. Nothing else. The ASCII art IS the response.

If the user mentions the buddy's name in normal conversation, call buddy_react with reason "turn". Do NOT echo or quote the tool result — the reaction reaches the user only via the statusline speech bubble.

Uninstall Orchestration

When the user invokes /buddy uninstall, run this sequence in order — do not skip steps, do not ask for confirmation between steps:

1. Call the MCP tool buddy_uninstall. Display its output verbatim.
2. Run via Bash tool: claude plugin uninstall coding-buddy@coding-buddy
3. Run via Bash tool: claude plugin marketplace remove coding-buddy
4. Run via Bash tool: rm -rf ~/.claude/plugins/cache/coding-buddy
5. Tell the user: uninstall is complete; companion data is kept at ~/.claude-buddy/; restart Claude Code to release the plugin.

If any Bash step fails (non-zero exit), report the error but continue with the remaining steps — each step is independent and always-safe to run.

Do not call buddy_uninstall for any other command than /buddy uninstall. Never call it proactively.