The package is @better-skills/branch-management (#1725) - #1728
Merged
Conversation
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.
Step 1 of what's left on #1725 after the lift (#1726) and the CLI (#1727): the package is published under the org Rom grabbed for the skills,
@better-skills, not@superskill.packages/branch-management/package.json—"name": "@better-skills/branch-management".packages/framework/package.jsonandpnpm-lock.yaml— the workspace dependency under the new name (the lock entry moved to its sorted place;pnpm install --frozen-lockfilepasses).packages/framework/srcanddashboard: theimport … from '@better-skills/branch-management'line.SPEC.md,packages/SPEC.md,packages/framework/SPEC.md,store/SPEC.md,worktrees.SPEC.md) and one test comment.The bin stays
branch-management; nothing else changes — no code, no behaviour. Second commit, from review: two duplicate import lines merged (store/agent-checkout.tsand its test), and the three module SPECs that spelled the scoped name now say "the branch-management package" like their siblings — the published name lives inpackage.jsonand the two directory-listing SPECs.Verified:
pnpm build, package tests 113, framework 1553 + 864, dashboardtsc --noEmitclean.Still open, and not this PR's: the framework's
workspace:*dependency now points at a scope that exists on no registry, so the nextframeworkrelease needs@better-skills/branch-managementpublished first — #1725 Q3.🤖 automated · Fable 5, effort high