feat(check): score fix, break, efficiency and speed in one block
🧪 Test / 🧪 Lock + lint (push) Canceled after 0s

kvb-check-efficiency measures a change against its base: tokens.py counts skill text tokens and listing words, measure.py runs one command in a base worktree and the working tree (one run per side, the mean of five over 100, an estimate marked ~ when other processes load the CPU). kvb-check-speed reads wall time from the same run and is not relevant for skills. kvb-check-score prints fix, break, efficiency, speed and the product score with emojis plus a gate line: below 90/5 it reports, over 100 it requires asking the operator before the commit.

Every skill that reported confidence and break risk now shows the score block; the 90/5 bar adds efficiency and speed at most 100. Commit blocks and the commit call's approval prompt name worktree, branch, diff stat and the score values, also for merges. 24 descriptions were shortened to keep the skill listing within its 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-04 17:07:24 +01:00
1 parent 6fa0311704
commit 0343a2f3ce
46 files changed
+1145 -118

No files matched your search

+7 -7
View File
@@ -1,8 +1,8 @@
---
name: kvb-org-matrix
description: >
One matrix of everything in flight with confidence and break risk per
item. Trigger on "status", "übersicht", "wo stehen wir".
One matrix of everything in flight with the kvb-check-score line per item.
Trigger on "status", "übersicht", "wo stehen wir".
---
One-shot overview, no side effects: it reads state and reports it, never
@@ -33,14 +33,14 @@ you could not read:
One table, most-blocking first, one row per item:
| Item | State | Conf. | Break risk | Evidence / next step |
| Item | State | Score | Evidence / next step |
- **State**: `open`, `running`, `blocked`, `done`. `done` means verified (a
passing run, a green check, a reproduction that now succeeds); work that
merely looks finished is `open`.
- **Conf.** and **Break risk**: two separate percentages per the
`kvb-check-confidence` skill, only for rows that changed something; `-`
for pure observation rows.
- **Score**: the `kvb-check-score` line (🎯 fix, 💥 break, 🌱 efficiency,
⚡ speed, 🏆 score) per the `kvb-check-confidence` skill, only for rows
that changed something; `-` for pure observation rows.
- **Evidence / next step**: for `done` the strongest proof line (what ran,
what it returned), otherwise the single next action.
@@ -58,6 +58,6 @@ Then at most three lines:
a forgotten background job or an unpushed commit is what the matrix exists
to surface.
- Report what the poll returned, never a predicted result; a running item
has no confidence number yet.
has no score yet.
- One row per item, no per-item paragraphs; the operator asks when a row
needs explaining.