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:
1 parent
42b66e3ddf
commit
2fbbd7386c
16 files changed
+506
-25
No files matched your search
@@ -2,9 +2,8 @@
|
||||
name: kvb-code-tune
|
||||
description: >
|
||||
Find and apply performance optimizations (CI, deploy, build, gate, hot
|
||||
paths) without reducing logic, coverage or correctness. Trigger on
|
||||
/kvb-code-tune, a job dying on its time budget, a slower pipeline or deploy,
|
||||
or asked where time goes.
|
||||
paths) without losing logic or coverage. Trigger on /kvb-code-tune, a job
|
||||
hitting its time budget, a slower pipeline, or asked where time goes.
|
||||
---
|
||||
|
||||
# Tune
|
||||
@@ -205,6 +204,9 @@ failure, or only moves the cost somewhere the measurement does not look.
|
||||
proposals. Re-measure from the same source under the same conditions and
|
||||
report a before and an after number.
|
||||
5. Repeat until the next candidate is worth less than the run that measures it.
|
||||
6. Hand the prototypes and before/after harnesses of every kept candidate to
|
||||
the `kvb-code-transcend` skill, so the measurement stays in the repository
|
||||
as a benchmark or regression test.
|
||||
|
||||
## Output
|
||||
|
||||
|
||||
Reference in new issue
Block a user