feat(wrap): /wrap rules on whether a session can close, or hands it off - #40
Merged
Merged
Conversation
The end-of-session question — can I close this and delete the worktree? — gets answered by feel, and both failure modes cost: closing on an unpushed branch or an hour of dead ends that only lived in the context, or leaving half-finished worktrees nobody dares delete. /wrap forces one of two rulings: finish it now, or wrap it into something durable and say it's safe to delete. The test is what dies when the worktree dies, not what feels important. Four hard stops force finishing (the world outside the repo is mid-change, the trunk is worse than you found it, what's left is minutes of work, or you can't write the brief). Otherwise it picks the cheapest durable form that carries the work — sidenote, committed doc, issue, or pushed branch plus draft PR — writes a five-line brief including the approaches already rejected, confirms the artifact landed outside the worktree, and ends on a verdict line. A PR needs at least one commit, so "a PR with only a description" is either an issue or a PR whose diff is the brief committed as a doc; the ladder routes accordingly. Installer: the three hardcoded command copies become a COMMANDS array, mirroring SKILLS, so the next command is a one-word edit.
Merged
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
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.
The end-of-session question — can I close this and delete the worktree? —
gets answered by feel, and both failure modes cost: closing on an unpushed
branch or an hour of dead ends that only lived in the context, or leaving
half-finished worktrees nobody dares delete.
/wrap forces one of two rulings: finish it now, or wrap it into something
durable and say it's safe to delete. The test is what dies when the worktree
dies, not what feels important. Four hard stops force finishing (the world
outside the repo is mid-change, the trunk is worse than you found it, what's
left is minutes of work, or you can't write the brief). Otherwise it picks
the cheapest durable form that carries the work — sidenote, committed doc,
issue, or pushed branch plus draft PR — writes a five-line brief including
the approaches already rejected, confirms the artifact landed outside the
worktree, and ends on a verdict line.
A PR needs at least one commit, so "a PR with only a description" is either
an issue or a PR whose diff is the brief committed as a doc; the ladder
routes accordingly.
Installer: the three hardcoded command copies become a COMMANDS array,
mirroring SKILLS, so the next command is a one-word edit.