feat(check): security value, commit tables, MEDUSA install and kvb-think-choice

kvb-check-security gains security.py: it scans the changed files with MEDUSA, weights findings (critical -50, high -25, medium -10, low -2) and prints locations and counts only; without MEDUSA it asks for a review by hand passed as '~<n>'. kvb-check-score takes --security and --critical: the score multiplies by security/100, a critical finding blocks the commit (exit 4), security below 100 asks the operator like efficiency or speed over 100, and a 90/5 failure now lists every cause. --table and --commit-table print the values as markdown tables, shown before and after every commit.

make install installs MEDUSA with pipx unless it is on the PATH. The new kvb-think-choice skill offers open decisions as multiple choice and checkboxes.

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:48:42 +01:00
1 parent 0343a2f3ce
commit 62a0bcf7e9
12 files changed
+786 -123

No files matched your search

+17 -11
View File
@@ -19,12 +19,15 @@ description: >
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 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.
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.
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
@@ -37,8 +40,11 @@ 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 (its kvb-check-score block, evidence,
residuals).
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.
kvb-check-confidence skill (its kvb-check-score block with 🛡️ security
from `security.py` of kvb-check-security, evidence, residuals).
6. Close with the staged bundle's commit table (`score.py ...
--commit-table <worktree>`: 📁 worktree, 🌿 branch, 📊 diff stat, scores,
gate), what remains unstaged, and wait for the operator's commit
decision; never auto-commit the newly staged bundle. A gate exit 4 says
up front that the bundle cannot be committed until its critical finding
is fixed.