feat(kvb-git): wrap the pkgmgr worktree and gc commands as skills

kvb-git-branch-gc becomes kvb-git-branch-cleanup and kvb-git-orphans-find becomes kvb-git-worktree-orphans, which drops its own orphans.py for pkgmgr's output. New wrappers: kvb-git-gc, kvb-git-worktree-cleanup and kvb-git-worktree-up. kvb-cleanup, kvb-dream, AGENTS.md and README.md point at the new names. Merges only after the pkgmgr release that ships these commands.

🎯 Fix: 90 %
💥 Break: 3 %
💸 Cost: new
⏱️ Time: new
🛡️ Security: 100 %
🏆 Score: 87
🚦 Gate: cost new, time new: cleared by the operator's commit word for the Skills wrappers (2026-11-07)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 18dade9a48a84761bf0c3a9b35584367ae0cb0e4)
This commit is contained in:
Kevin Veen-Birkenbach committed 2026-11-12 10:38:42 +00:00
1 parent fd8fc08603
commit ebe7886654
17 files changed
+290 -807

No files matched your search

+52
View File
@@ -0,0 +1,52 @@
---
name: kvb-git-worktree-up
description: >
Check a branch out into a worktree.
---
`pkgmgr worktree up` creates the worktree: it fetches origin without
auto-maintenance, checks out an existing branch, tracks `origin/<branch>` or
creates the branch with `--no-track` from `--base` (origin's default branch
when omitted), assigns a slot and runs the pinned `worktree-init` hook. This
skill adds only the agent discipline.
## Step 1: claim and place
1. Claim the work through the `kvb-org-organize` skill first; its edit gate
blocks every edit in the new worktree without a claim.
2. Always pass `--path`, inside a directory the session released for
worktrees (Claude Code: a `sandbox.filesystem.allowWrite` root), else
`<repo>/.worktrees/<branch>` where the repository ignores `.worktrees/`.
pkgmgr's standard path under `directories.worktrees` only where that root
is released too: the sandbox cannot write anywhere else.
## Step 2: create
From inside the repository:
```bash
pkgmgr worktree up <branch> --path <dir> --json
```
`--base <ref>` only for a new branch that must not start at origin's default
branch. Read `path`, `origin`, `slot`, `hook` and `warnings`:
- **Exit 2** refused (path exists, invalid name, a filter or network setting
in the repository config): report the line; never `git worktree add`
around it.
- **Exit 1**: the `worktree-init` hook failed and the worktree stays; report
the hook output, no retry without the operator's word.
- **`hook` `not pinned: worktree-init in <Makefile>`**: pkgmgr ran no init,
because only the operator's pkgmgr config pins a hook (`worktree_hooks`,
keyed `<provider>/<account>/<repository>`); a Makefile target is reported,
never run. Say so; pinning is the operator's (`kvb-org-operator`), and the
project's rules decide whether an agent runs the target itself.
- **`warnings`** (`fetch failed`, `fetch skipped`): the base may be stale; say
so.
## Step 3: register
Record the worktree under the task in the `kvb-org-rasci` register:
`rasci.py set <task> --workdir <path> --branch <branch> --artifact
worktree:<path>`. It goes later through the `kvb-git-worktree-cleanup` skill,
never by hand.