fix(help): tell users where to run /buddy CLI commands from - #112
Open
grlee wants to merge 1 commit into
Open
Conversation
The /buddy help output lists CLI commands as `bun run show`, `bun run pick`,
etc., but never tells users where to run them from. The plugin lives in
~/.claude/plugins/cache/claude-buddy/claude-buddy/<version>/, which is not
an obvious location, and running `bun run <cmd>` from outside that directory
fails with a confusing "no script named X" error.
Replaces the bare "CLI:" header with a hint that includes a path-finder
one-liner so users can cd into the plugin directory first:
cd "$(ls -d ~/.claude/plugins/cache/claude-buddy/claude-buddy/*/ | tail -1)"
The hint respects $CLAUDE_CONFIG_DIR via the ~/.claude default that the rest
of the plugin already assumes; users who relocate Claude Code's config can
substitute their own path.
No code-path changes; only the static help-text string.
Signed-off-by: George Lee <grlee@users.noreply.github.com>
grlee
force-pushed
the
fix/cli-help-discoverability
branch
from
June 10, 2026 11:54
bd370e9 to
f443b77
Compare
Owner
|
Hey @grlee — good catch on the discoverability gap, and the fix is the right shape. One thing before merge: the project was just renamed (claude-buddy → coding-buddy, now also shipping Pi / Oh My Pi extensions), so the cache path in the new help text is stale. Could you update it to: Once that's updated this is good to go. 🤖 Created with the help of AI (Claude Fable 5). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
/buddy helplists CLI commands like:…but never tells users where to run them from. The plugin lives at:
which isn't an obvious location. Running
bun run showfrom any other directory fails with a confusingerror: Script not found "show"error from bun, leaving users wondering whether the install is broken.Fix
Replaces the bare
"CLI:"header in the help text with a hint that includes a path-finder one-liner:3 lines added, 1 line removed. No code-path changes — just the static help string. The path uses
~/.claudebecause that's the default the rest of the plugin already assumes; users who relocate Claude Code's config via$CLAUDE_CONFIG_DIRcan substitute their own path.Verification
bun run typecheckpasses.bun testpasses — 246/246 tests.Out of scope
buddybinary on PATH). Larger architectural change, separate concern.