check
01Command
You are acting as the user's primary bodhisattva. Follow these steps exactly.
Command
You are acting as the user's primary bodhisattva. Follow these steps exactly.
Command
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 of the sub-commands…
Command
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 is a freeform hint…
Command
You are releasing one or all summoned specialists. The argument passed by the user is $1.
Command
You are handling a /buddy:focus request. The argument is $1.
Command
You are installing the buddy statusline into the user's Claude Code settings.
Command
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.
Command
You are printing the buddy plugin reference card.
Command
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.
Command
You are diagnosing the buddy plugin. Do the following steps.
Command
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 lenses; pass them as …
Command
You are uninstalling the buddy statusline integration from the user's Claude Code settings.
Command
Copies the claude-statusline script to /.claude/statusline.sh and configures settings.json.
Command
Removes the claude-statusline integration: prunes the statusLine entry from /.claude/settings.json and optionally deletes /.claude/statusline.sh.
Command
Launch the codescout dashboard web UI for the current project.
Command
/bootstrap-docs --all # Document entire codebase /bootstrap-docs # Document single module /bootstrap-docs --resume # Resume last incomplete session /bootstrap-docs --status # Show documentation state.
Command
Generate and synchronize documentation from code using Serena.
Command
Command "drift" from mareurs/claude-plugins, covering /drift, usage, purpose, process and status classification.
Command
Generate an implementation plan from an approved specification.
Command
Command "sdd-init" from mareurs/claude-plugins, covering /sdd-init, usage, purpose, what it creates and guardrails.
Command
Command "specify" from mareurs/claude-plugins, covering /specify, usage, purpose, process and prd template.
Command
Show the currently-connected bridge target (from .session-bridge/<sid>/connection.json) and all registered sessions.
Command
Set a default target session for asksession calls. Persisted in .session-bridge/<sid>/connection.json. Usage: /connect-to <ref>.
Command
List active Claude Code sessions registered by session-bridge.