Conversation
The skill too often skipped creating the worktree on a judgment that the task (research, read-only) didn't need isolation. Its lead was only an ordering rule and Scope's "authorizes" read as permission, inviting that necessity test. State the contract instead: invoking the command is itself the explicit request to create the worktree; rationale.md records the failure mode so the wording isn't softened back. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
worktrunk-bot
approved these changes
Jul 3, 2026
cedoi93-svg
approved these changes
Jul 4, 2026
cedoi93-svg
approved these changes
Jul 4, 2026
cedoi93-svg
approved these changes
Jul 4, 2026
cedoi93-svg
approved these changes
Jul 4, 2026
Merged
max-sixty
added a commit
that referenced
this pull request
Jul 8, 2026
Release v0.66.0 — minor bump (semver-checks: `ListConfig` gained a pub field, so patch is disallowed pre-1.0). ## Changes since v0.65.0 ### Improved - **Opt-in JSON schema 2 for `wt list`** behind the `[list] json-schema` config key ([#3357](#3357)) - **`wt config approvals list` and `clear --stale`** ([#3380](#3380)) ### Fixed - **User hooks no longer inherit `wt`'s `GIT_*` discovery vars** ([#3374](#3374), thanks @silvanshade for reporting) — this entry also moves from the 0.65.0 CHANGELOG section (where #3374 misfiled it post-release) into 0.66.0, which ships it. ### Documentation - **`/wt-switch-create` always creates a worktree** ([#3356](#3356)) ## Release validation - Local pre-merge gate: 4,357 tests green - Nightly cross-platform run on the cut-from tip (9edf0aa): all 12 jobs green ([run](https://github.com/max-sixty/worktrunk/actions/runs/28842962865)) - Data-loss surface review: four independent finders, three candidates adjudicated acceptable, signed off - Changelog entries verified against the actual diffs 🤖 Generated with [Claude Code](https://claude.com/claude-code) > _This was written by Claude Code on behalf of Maximilian Roos_
1 task
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
3 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.
/wt-switch-createtoo often skipped creating the worktree, judging that a research or read-only task didn't need isolation. Two wordings invited that: the lead was only an ordering rule ("steps 1–3 come before any other work"), and Scope's "authorizes" read as permission, prompting a should-I test that user-level rules gating worktree creation behind explicit request answer with "no".The lead now states that invoking the command is itself the explicit request (a research task gets a worktree all the same), Scope states the mandate's bounds without permission language, and rationale.md records the failure mode so the wording isn't softened back.
Prose-only; no code or generated docs touched.