Stats
Actions
Tags
From buddy-evolver
This skill should be used when the user asks to "buddy reset", "reset buddy", "restore buddy", "revert buddy", "undo buddy changes", or "get my original buddy back".
How this skill is triggered — by the user, by Claude, or both
Slash command
/buddy-evolver:buddy-resetThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Restore the user's original Claude Code Buddy by reverting companion data to the pre-evolution state.
Restore the user's original Claude Code Buddy by reverting companion data to the pre-evolution state.
echo "Soul backup exists: $(test -f ~/.claude/backups/.claude.json.pre-customize && echo 'yes' || echo 'no')"
echo "Metadata exists: $(test -f ~/.claude/backups/buddy-patch-meta.json && echo 'yes' || echo 'no')"
If the soul backup does not exist, tell the user there is nothing to restore and exit.
plutil -extract companion json -o - ~/.claude.json 2>/dev/null || echo "{}"
Display the current name and personality so the user knows what they are reverting from.
Ask: "This will restore your original companion data and remove the buddy card. Continue?"
"${CLAUDE_PLUGIN_ROOT}/scripts/run-buddy-patcher.sh" --restore
Tell the user:
Your original buddy has been restored.
Changes take effect on your next Claude Code conversation — no restart needed.
Run /buddy-status to confirm the card is cleared.
To re-evolve at any time, run /buddy-evolve.
npx claudepluginhub soul-craft/buddy-evolver --plugin buddy-evolverManages a coding companion via /buddy command. Shows, pets, renames, or configures the companion using MCP tools. Includes fallback diagnostics for MCP server issues.
Manages Claude Code user configs (~/.claude/, ~/.claude.json): storage cleanup, backup/restore, reset with MCP preservation, history/plans/sessions/stats, health audits.