feat: plugin ships commands + skill only, not hooks#122
Merged
Conversation
A Claude Code plugin installs at user scope by default, so bundling the observe/inject hook dispatcher (hooks/hooks.json) made it fire in every repo — double-recording and injecting an unwanted instinct block in any repo already running its own learning loop. Commands and the using-bough skill are inert until invoked, so they are safe user-scoped; hooks are not. Drop hooks/hooks.json and its drift test (internal/hooks/plugin_sync_test.go) from the plugin. Observation stays wired by the CLI, scoped to the project the operator chooses: `bough hook install --scope project|user`. Remove the now- obsolete "plugin double-fires / run bough hook uninstall" heads-up from `bough doctor` (the plugin no longer carries hooks, so the note was misleading). Verified: isolated `claude plugin install bough@bough` now reports Skills (12) + Hooks (0); full unit suite green. Docs (README, docs/PLUGIN_CLAUDE_CODE.md, using-bough SKILL) updated to the "install the plugin anywhere / observe only where you `bough hook install`" model.
ikeikeikeike
force-pushed
the
feat/plugin-commands-skills-only
branch
from
July 16, 2026 17:52
9c70c73 to
82fbdd4
Compare
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
1 participant
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.
A Claude Code plugin installs at user scope by default, so bundling the observe/inject hook dispatcher (
hooks/hooks.json) made it fire in every repo — double-recording and injecting an unwanted instinct block in any repo already running its own learning loop. Commands and theusing-boughskill are inert until invoked, so they are safe user-scoped; hooks are not.Drop
hooks/hooks.jsonand its drift test from the plugin. Observation stays wired by the CLI, scoped to the project the operator chooses:Also removes the now-obsolete "plugin double-fires / run
bough hook uninstall" heads-up frombough doctor(the plugin no longer carries hooks, so the note was misleading).claude plugin install bough@bough~/.claudeuntouchedgo build/golangci-lint ./internal/hooks/internal/ cmd/ pkg/)claude plugin validateTest
TestDoctorRender_PluginDoubleWireNote→TestDoctorRender_NoPluginDoubleWireNote(regression guard: the obsolete note must not come back). Docs (README,docs/PLUGIN_CLAUDE_CODE.md,using-boughSKILL) updated to the "install the plugin anywhere / observe only where youbough hook install" model.