docs(skills): add restart trigger phrases for discoverability#106
Merged
Conversation
HiveMind Sessions1 session · 3m · $0.32
View all sessions in HiveMind → Run |
Route "restart the weave daemon" / "weave is on an old config" requests to the existing config and status skills instead of adding a fourth skill for the single-command restart flow. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
… body The skill's description was updated to route stale-config questions here, but the body never mentioned the new ⚠ state or its fix. Add the warning state to the legend, give it a row in the issues table with the restart command, and instruct the Report step to surface ⚠ warnings explicitly. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
rgao-coreweave
force-pushed
the
feat/restart-discoverability
branch
from
fc4a444 to
a2a743c
Compare
andrewtruong
approved these changes
Jun 22, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Summary
weave-configdescription picks up "restart the weave daemon" / "apply weave config changes" / "restart weave to pick up changes" so requests after a settings change route here. Body already coversweave-claude-code restart.weave-statusdescription picks up "weave is running an older config" / "the daemon is on an old config" so the feat(status): warn when the daemon is running an older config #102 warning routes here. Body now documents the⚠state, gives the stale-config warning a row in the issues table with the restart fix, and tells the Report step to surface⚠explicitly.Why not a new skill
restartis decision-free, already surfaced byweave-config(after a setting change) andweave-status(when the daemon is stale). A standalone skill adds surface area for no interpretation;logs/daemon/uninstalllikewise have no skill.Test plan
npm test