The package is @better-skills/branch-management (#1725) (#1728)

* The package is @better-skills/branch-management (#1725)

* Review: one import line, one name for the package in the module SPECs

Author: suleimansh

SPEC.md

@@ -3,7 +3,7 @@ The Framework: autonomous AI programming. Humans make the important decisions; c
 Four top-level pieces, one product:
 
 - `packages/framework` — the product itself, published as the npm package `framework`: one CLI (`the-framework`) that runs a foreground daemon, the agent lifecycle it orchestrates, and the browser dashboard it serves — the product's only user interface.
-- `packages/branch-management` — the git conventions and operations behind an agent's own checkout, as an API and as the `branch-management` command every agent the daemon starts on its machine gets on its PATH, published as `@superskill/branch-management`: the first of the skills the product is being split into, and the only one so far. The product depends on it; it depends on nothing of the product.
+- `packages/branch-management` — the git conventions and operations behind an agent's own checkout, as an API and as the `branch-management` command every agent the daemon starts on its machine gets on its PATH, published as `@better-skills/branch-management`: the first of the skills the product is being split into, and the only one so far. The product depends on it; it depends on nothing of the product.
 - `packages/chrome-extension` — the Claude web bridge, a companion Chrome extension: when an agent's task was handed to a Claude Code cloud session on claude.ai, it carries the question that session is parked on into the local dashboard, and types the answer picked there back into the session.
 - `packages/the-framework.ai` — the marketing website at https://the-framework.ai.
 

packages/SPEC.md

@@ -1,7 +1,7 @@
 The deliverables The Framework ships, one directory each:
 
 - `framework/` — the product: the `framework` npm package (CLI, daemon, agent lifecycle, dashboard).
-- `branch-management/` — the `@superskill/branch-management` npm package: the git conventions and operations behind an agent's own checkout, the first skill of the skills-plus architecture (#1725). The product depends on it; nothing else does yet.
+- `branch-management/` — the `@better-skills/branch-management` npm package: the git conventions and operations behind an agent's own checkout, the first skill of the skills-plus architecture (#1725). The product depends on it; nothing else does yet.
 - `chrome-extension/` — the Claude web bridge, a companion Chrome extension that connects Claude Code cloud sessions on claude.ai back to the local dashboard.
 - `the-framework.ai/` — the marketing website.
 

packages/branch-management/package.json

@@ -1,5 +1,5 @@
 {
-  "name": "@superskill/branch-management",
+  "name": "@better-skills/branch-management",
   "version": "0.0.0",
   "description": "Branch management for coding agents: one git checkout per agent under .the-framework/branches/, named as its branch, reclaimed once its work is on the remote.",
   "license": "MIT",

packages/framework/SPEC.md

@@ -2,7 +2,7 @@ The product: the `framework` npm package. One CLI, `the-framework`, runs a foreg
 
 How the package's pieces relate:
 
-- `src/` — everything that runs in Node: the CLI, the daemon, the agent lifecycle (checkouts through the `@superskill/branch-management` package, gates, handoff), the driver seam that wraps each coding-agent CLI, the data branch, autonomy (Auto PM, sweeps, CI watch), and the server side of the dashboard.
+- `src/` — everything that runs in Node: the CLI, the daemon, the agent lifecycle (checkouts through the branch-management package, gates, handoff), the driver seam that wraps each coding-agent CLI, the data branch, autonomy (Auto PM, sweeps, CI watch), and the server side of the dashboard.
 - `dashboard/` — the browser app the daemon serves: a single-page app that is a pure projection of the files the daemon writes, reading over `POST /_rpc/<name>` and a live event stream, and steering agents back through the same daemon.
 - `prompts/` — every prompt The Framework sends an agent, as markdown: the built-in system prompt, the protocols agents answer through, and the presets. The markdown is the only source of truth for agent-facing text.
 - `scripts/` — the build steps that compile the prompts into importable strings and run the package's test suites.

packages/framework/package.json

@@ -46,7 +46,7 @@
   },
   "dependencies": {
     "@base-ui-components/react": "1.0.0-rc.0",
-    "@superskill/branch-management": "workspace:*",
+    "@better-skills/branch-management": "workspace:*",
     "@puppeteer/browsers": "3.2.1",
     "@shadcn/react": "^0.2.1",
     "@tiptap/core": "^2.10.0",

packages/framework/src/agent-archive.test.ts

@@ -1,7 +1,7 @@
 import { strict as assert } from 'node:assert'
 import { test } from 'node:test'
 import { join } from 'node:path'
-import type { GitRunner } from '@superskill/branch-management'
+import type { GitRunner } from '@better-skills/branch-management'
 import { userDirName, resolveUserDir, forgetUserDirs, ANONYMOUS_USER_DIR } from './agent-archive.js'
 import { frameworkGitignore } from './framework-gitignore.js'
 

packages/framework/src/agent-archive.ts

@@ -1,5 +1,5 @@
 import { ARCHIVE_DIR } from './store/index.js'
-import { nodeGitRunner, type GitRunner } from '@superskill/branch-management'
+import { nodeGitRunner, type GitRunner } from '@better-skills/branch-management'
 /**
  * Committed session history (#1179): where a project's finished agents are archived so they survive
  * the repo being cleaned.

packages/framework/src/agent.test.ts

@@ -608,7 +608,7 @@ test('runAgent runs the backlog loop after the build when opted in (#323)', asyn
   const { mkdtemp, realpath, rm, writeFile } = await import('node:fs/promises')
   const { tmpdir } = await import('node:os')
   const { join } = await import('node:path')
-  const { nodeGitRunner } = await import('@superskill/branch-management')
+  const { nodeGitRunner } = await import('@better-skills/branch-management')
   const { withDataBranch } = await import('./data-branch.js')
   // The queue lives on the data branch (#1582), so the fixture is a real repo.
   const git = nodeGitRunner()

packages/framework/src/cli.test.ts

@@ -6,7 +6,7 @@ import { join, dirname } from 'node:path'
 import { appendControl } from './control.js'
 import { BROWSER_MCP_SERVERS, withBrowser } from './browser.js'
 import { EVENTS_FILE, ARCHIVE_DIR, type StoreFs } from './store/index.js'
-import { FRAMEWORK_DIR, nodeGitRunner } from '@superskill/branch-management'
+import { FRAMEWORK_DIR, nodeGitRunner } from '@better-skills/branch-management'
 import { layoutMarker, layoutMarkerPath } from './layout.js'
 import {
   chooseSessionLink,

packages/framework/src/cli.ts

@@ -45,7 +45,7 @@ import {
 import { loadUserSystemPrompt, SYSTEM_PROMPT_FILE } from './system-prompt-file.js'
 import { checkForUpdate, formatUpdateStatus, nodeVersionFetcher, type VersionFetcher } from './update-check.js'
 import { AgentStore, nodeStoreFs, type StoreFs } from './store/index.js'
-import { currentBranch, nameBranch, agentBranchName, nodeGitRunner } from '@superskill/branch-management'
+import { currentBranch, nameBranch, agentBranchName, nodeGitRunner } from '@better-skills/branch-management'
 import { materializePresets } from './presets.js'
 import { isLoopbackHost, registerHomeProject, runDaemon, DEFAULT_DAEMON_HOST, DEFAULT_DAEMON_PORT } from './daemon.js'
 import { appendControl, resetControl, watchControl, type ControlWatcher } from './control.js'