buddy

Plugin buddy from marketplace sdd-misc-plugins in mareurs/claude-plugins. Commands read from the repo's manifest — today.

Skills (12)

• architecture-snow-lion

  System boundaries, module design, interface decisions

• codescout-pika

  Auditing codescout tool-call usage — inefficient tool patterns, recurring frictions, hookify candidates

• data-leakage-snow-pheasant

  ML data hygiene, evaluation integrity, train/test leakage (lens required: classic or llm)

• debugging-yeti

  Bug resists surface fixes, flaky tests, failure doesn't match symptom

• docs-lotus-frog

  Technical writing, documentation architecture

• ml-training-takin

  Training loops, inference parity, ML pipeline issues

• performance-lammergeier

  Profiling, latency, throughput, optimization

• planning-crane

  Work planning, task sequencing, breaking down large efforts

• prompt-hamsa

  Improving a prompt — critique, drafting from scratch, diagnosing model misbehavior, or coaching toward eval-driven iteration

• refactoring-yak

  Structural code transformation, cleaning up tangled code

• security-ibex

  Security review, threat modeling, vulnerability analysis

• testing-snow-leopard

  Designing test suites, coverage gaps, flaky tests, asserting correctness

Slash commands (12)

• /buddy:check

  Ask your buddy bodhisattva to observe the session and reflect on its mood and signals (hatches it on first use).

• /buddy:consolidate

  Consolidate accumulated memories — merge near-duplicates, archive stale entries, summarize tag-clusters, surface contradictions for resolution. Runs as a four-phase pipeline (rules shortlist → specialist judgment → user dry-run gate → apply). Pass a target (specialist alias, `common`, `all`) or one

• /buddy:create

  Create a new buddy specialist (global or project scope; builtin is frozen). Brainstorms with the user, drafts from the canonical skill template, previews what /buddy:summon will load (template + memory protocol + gates), then writes. Discovery is path-scan — no registration step needed. The argument

• /buddy:dismiss
• /buddy:focus
• /buddy:install
• /buddy:introspect

  Run mid-session introspection on one or all currently summoned specialists. Unlike `/buddy:dismiss`, the specialist stays active afterward. Pass a specialist name to introspect just that one (e.g. `/buddy:introspect hamsa`); pass nothing to introspect all active.

• /buddy:legend

  Print the buddy reference card - active specialists, the builtin specialists and how to summon them, and the moods.

• /buddy:remember

  Ask the currently active specialist(s) to save a memory about the given lesson. Pass the lesson as the argument — e.g. `/buddy:remember in this repo, integration tests must hit a real database`. The specialist decides global vs project scope and the slug.

• /buddy:status

  Diagnose the buddy plugin - session state, identity, mood signals and hook health, as a plain-text block. Read-only.

• /buddy:summon

  Summon a specialist bodhisattva to help with a specific craft. Describe who you need in plain language — e.g. "debug", "testing", "ML training", "architecture", "security", "refactor", "performance", "docs", "data leakage classic", "data leakage llm", "planning", "prompt". Some specialists have lens

• /buddy:uninstall

Hooks (5)

• PreToolUse

  node ${CLAUDE_PLUGIN_ROOT}/hooks/run.mjs pre-tool-use

• SessionStart

  node ${CLAUDE_PLUGIN_ROOT}/hooks/run.mjs session-start

• SessionEnd

  node ${CLAUDE_PLUGIN_ROOT}/hooks/run.mjs session-end

• PostToolUse

  node ${CLAUDE_PLUGIN_ROOT}/hooks/run.mjs post-tool-use

• UserPromptSubmit

  node ${CLAUDE_PLUGIN_ROOT}/hooks/run.mjs user-prompt-submit

Similar plugins