docs(agents): suggest the magicbean Claude Code plugin when it isn't installed #935
No reviewers
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!935
Loading…
Reference in a new issue
No description provided.
Delete branch "HumanBean/Longshot:docs/claude-plugin-setup"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type: docs · Risk: low · Tested on: n/a (docs only) · Needs: none
Why
Contributors who use Claude Code often don't have the team's
magicbeanplugin, so/magicbean:team-updates,/magicbean:releaseand/magicbean:batch-revieware missing and their agents skip the team chat and release flow. Nothing in CONTRIBUTING.md or AGENTS.md told them, or their agent, to install it.What changed
CONTRIBUTING.md and AGENTS.md now say how to install the plugin, and AGENTS.md tells an agent to check for it and suggest it when it is missing. The same change goes to LongshotLauncher and Tooling.
CONTRIBUTING.md: a "Using Claude Code?" note under Get the team's tooling and sign in, with the two/plugincommands.AGENTS.md: a bullet telling the agent to runclaude plugin list, and whenmagicbean@magicbeanis missing, to tell the person at session start and give them the two commands (plugin commands are theirs to run).Measurements
Verdict: nothing to measure: documentation only, no game code.
Flags and settings
None
Testing
Tested: the install commands are the ones in Tooling's README; I ran them on this PC and the plugin loaded (
/reload-plugins).Not tested: the test suite was not run here; it reads no Markdown.
Must be tested: None.
Risks
What could break: nothing; text only.
Turning it off: revert the commit.
Compatibility: Nothing changes.
Checklist
Everyone
type(scope): description) of the status line's type.main.python -I -B tests/run_all.pypasses (not run locally; CI skips the Python checks for a docs-only change)third_party/untouched (a new folder with aPROVENANCE.mdinstead).When it applies
Assisted-by:/Co-Authored-By:trailers.Added the Flags and settings subsection (None). The tests box stays unticked until CI has run the checks.
Ticked the checks box: CI's Python source checks are skipped for a docs-only change.
WIP: docs(agents): suggest the magicbean Claude Code plugin when it isn't installedto docs(agents): suggest the magicbean Claude Code plugin when it isn't installedmooki referenced this pull request2026-11-15 22:24:10 +00:00