Harden /update skill — lore preview, confirmation gate, staging default#79
Open
Harden /update skill — lore preview, confirmation gate, staging default#79
Conversation
- Gatekeeper framing: opens with safety warning, "never pull without explicit confirmation" - Fix default branch fallback: "main" → "staging" - Step 3 rewritten with lore-tone instructions: lodge bulletin style, not changelog. Includes good/bad examples and rules for leading with the cool stuff, naming risks briefly - Step 4: explicit AskUserQuestion requirement — must pause for user yes/no, lists accepted phrases, no implicit consent - Step 5: structured action items per change type (bot restart, container restart, env vars, server auto-reload) - Notes: clarified auto-reload behavior, added "err on side of flagging" Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
What changed
The
/updateskill is now a proper safety gate for woltspace platform updates.Before: dry changelog tone, wrong default branch (
main), no hard confirmation requirement.After: lodge gatekeeper. Speaks like it lives here. Won't move until you say go.
Changes
"main", now"staging"(where platform work lands)AskUserQuestionto pause and wait for explicit yes. Lists accepted phrases. "What's new?" is not a yes.--watchauto-reload behavior, "err on side of flagging" addedWho this affects
All wolts.
/updateis how wolts pull platform changes — this lands for everyone on their next update.🤖 Generated with Claude Code