Kevin Veen-BirkenbachandClaude Opus 5.5
0343a2f3ce
🧪 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>
1.6 KiB
1.6 KiB
name, description
| name | description |
|---|---|
| kvb-code-scope-guard | Deliver exactly what was asked. Trigger on every task creating files, commands or commits, on autonomous runs and hand-overs, and when asked why something unrequested exists. |
The requested scope is the deliverable. A problem you noticed behind the request is not an invitation to solve it.
Before creating anything the request did not name, answer one question: which sentence of the request asks for this? No sentence, no artifact.
- No permanent scaffolding for a one-off need. A migration you run once needs a throwaway script, not a CLI subcommand that ships forever. Do the thing, then delete the scaffolding.
- Path-scope every
git add. Never-A, never.. The operator's tree carries their own edits and their local config, and sweeping those into your bundle makes them undo your work by hand. - An adjacent defect gets reported in one line, not fixed, unless it blocks the request. Fixing it quietly puts an unreviewed change in someone else's commit.
- An instruction to hand something over is complete on its own. Print the artifact in the shape asked for: do not optimize, reorder or deduplicate it, do not wrap it in a command that consumes it, and do not append commentary, next steps, confidence blocks or offers. A narrowing qualifier ("just the line") re-shapes the earlier request; re-emit narrower without re-deriving the content. A problem with the artifact is worth one sentence before it, never a rewrite of it.
When something genuinely seems missing, say so in one sentence and finish the requested scope anyway. Widening the scope is the operator's call.