feat(score): value quotient and gate values in commit messages

tokens.py weighs the daily token cost of a skill change from the last 7 days of transcripts against its value and prints a 💰 n:n line; tokens.py value --since <commit> measures the value after shipping. score.py takes --value as a 💰 column and prints --message-block, one gate value per line, which commit-no-verify and commit-next now require as its own paragraph in every commit message.

🎯 Fix: 93 %
💥 Break: 2 %
🌱 Efficiency: 117 %
⚡ Speed: –
🛡️ Security: ~100 %
💰 Value: ?
🏆 Score: 78
🚦 Gate: ⚠️ efficiency 117 % > 100: ask the operator before the commit

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 19:22:53 +01:00
1 parent 62a0bcf7e9
commit 03c56f0801
8 files changed
+646 -65

No files matched your search

+9 -7
View File
@@ -21,13 +21,15 @@ description: >
(kvb-code-no-comments audit and kvb-check-legal check first, then the
full staged diff and the kvb-check-score commit table of 📁 worktree,
🌿 branch, 📊 diff stat, scores with 🛡️ security and gate, then
`git commit --no-verify`, exact staging index only, then the table again
with the hash). Its approval-prompt duty is binding: the commit call's
approval prompt names worktree, branch, diff stat and the score values
with 🛡️ security, or the call is not sent. Gate exit 4 (critical security
finding): no commit, the call is never sent. Exit 1 is shown and the
operator's word decides; exit 3 asks the operator again first, naming
each cause.
`git commit --no-verify`, exact staging index only, its message carrying
the `score.py --message-block` paragraph right before the
`Co-Authored-By` line as one `-m` argument, then the table again with the
hash). Its approval-prompt duty is binding: the commit call's approval
prompt names worktree, branch, diff stat and the score values with
🛡️ security, and the message holds the block, or the call is not sent.
Gate exit 4 (critical security finding): no commit, the call is never
sent. Exit 1 is shown and the operator's word decides; exit 3 asks the
operator again first, naming each 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