feat(transcend): carry session scripts, tests and skills into the repos

Adds kvb-transcend (collector), kvb-skills-transcend (into the skills repo) and kvb-code-transcend (into the current repo). transcend.py scans the own scratchpad, peer scratchpads and the agent homes for scripts, tests and skills the skills repo does not ship, skips secret-named and oversized files, and remembers carried/dropped decisions by content digest in the gitignored .state/transcend.json, so a rescan offers only new or changed candidates. Wired into kvb-skills-tune (own scripts), kvb-code-tune step 6 (measurements) and kvb-skills-dream step 7. Seven descriptions are tightened to stay inside the 1300-word listing budget.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Kevin Veen-BirkenbachandClaude Opus 5.5 committed 2026-11-03 13:57:14 +01:00
1 parent 42b66e3ddf
commit 2fbbd7386c
16 files changed
+506 -25

No files matched your search

+62
View File
@@ -0,0 +1,62 @@
---
name: kvb-code-transcend
description: >
Carry the session's ad-hoc tests and scripts into the current repo.
Trigger on /kvb-code-transcend.
---
The test the agent ran from its scratchpad, the probe that proved a cause, the
benchmark behind an optimization: they protected this session's work and
nothing after it. This skill moves them into the repository the agent works
in (`git rev-parse --show-toplevel`), in that repository's own form. It
changes nothing before the operator confirms.
## Step 1: inventory
Read-only:
- **Tests and scripts outside the repo**: `transcend.py scan` of the
`kvb-transcend` skill lists them in the own and peers' scratchpads and
skips what was already decided and has not changed; peer candidates follow
that skill's consent step. Add the `python -c` checks and negative controls
this session ran inline.
- **Probes and reproductions** that proved a root cause or a fix.
- **Measurements**: prototypes and before/after harnesses of the
`kvb-code-tune` skill.
- **Repeated commands** a make target or script of the repository could own.
- **Untracked helpers** the agent left inside the repository.
One line each: `candidate -> source -> what it guards`.
## Step 2: classify
Read the repository's rules first (AGENTS.md, CONTRIBUTING, the Makefile, the
test layout). Per candidate one target in that repository's form: a test in
its test tree and framework, a make target, a script under its scripts
directory, a CI step, or drop. No new framework, dependency or language
without the operator. A kept optimization keeps its measurement as a
benchmark or regression test.
## Step 3: listen and confirm
Run the `kvb-think-listen` skill on the open points: target path, framework,
which repository line owns the file. Then `AskUserQuestion`: one
`multiSelect` with the candidates, nothing preselected, and per pick a
single-select `Write it` / `Revise it` / `Discard` with the drafted diff.
## Step 4: write
- Write only the confirmed files, path-scoped; a peer's line goes to its
owner through the `kvb-org-coordinate` skill.
- Every carried test fails without the code it guards: show the negative
control once.
- Run the repository's tests only on the resource chair's grant (the
`kvb-org-organize` skill); leave the result uncommitted for the
`kvb-git-commit-next` skill.
- `transcend.py mark` every offered candidate with its verdict.
## Output
| Candidate | Source | Target in the repo | Verdict |
Dropped candidates stay with their reason.