feat(check): score fix, break, efficiency and speed in one block
🧪 Test / 🧪 Lock + lint (push) Canceled after 0s
🧪 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:
1 parent
6fa0311704
commit
0343a2f3ce
46 files changed
+1145
-118
No files matched your search
@@ -18,9 +18,13 @@ description: >
|
||||
Wait for the operator's decision; do not commit.
|
||||
3. Nothing similar found, or the operator picked the staged version: run the
|
||||
kvb-git-commit-no-verify skill on the currently staged changes
|
||||
(kvb-code-no-comments audit and kvb-check-legal check first, then its
|
||||
four-line block of worktree path, branch, fix confidence and break risk,
|
||||
then `git commit --no-verify`, exact staging index only).
|
||||
(kvb-code-no-comments audit and kvb-check-legal check first, then the
|
||||
full staged diff and its score block of 📁 worktree, 🌿 branch,
|
||||
📊 diff stat, score line and gate line, then `git commit --no-verify`,
|
||||
exact staging index only). Its approval-prompt duty is binding: the commit
|
||||
call's approval prompt names worktree, branch, diff stat and the score
|
||||
values, or the call is not sent. Gate exit 1 is shown and the operator's
|
||||
word decides; exit 3 asks the operator again first, naming the cause.
|
||||
4. Group the remaining uncommitted changes into logical bundles (one concern
|
||||
per bundle: same failure class, mechanism or role) and stage the next one;
|
||||
never mix concerns to save a commit. Staging happens here and nowhere
|
||||
@@ -33,7 +37,8 @@ description: >
|
||||
<worktree> --file <path> --match <regex>`, first with `--dry-run`.
|
||||
5. For the newly staged bundle run the kvb-think-explain skill (what the
|
||||
changes do and how the pieces interact, file:line-anchored), then the
|
||||
kvb-check-confidence skill (fix confidence, break risk, evidence,
|
||||
kvb-check-confidence skill (its kvb-check-score block, evidence,
|
||||
residuals).
|
||||
6. Close with what remains unstaged and wait for the operator's commit
|
||||
decision; never auto-commit the newly staged bundle.
|
||||
6. Close with the staged bundle's score block (📁 worktree, 🌿 branch,
|
||||
📊 diff stat, score line, gate line), what remains unstaged, and wait for
|
||||
the operator's commit decision; never auto-commit the newly staged bundle.
|
||||
Reference in new issue
Block a user