Kevin Veen-BirkenbachandClaude Opus 5.5
62a0bcf7e9
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>
2.0 KiB
2.0 KiB
name, description
| name | description |
|---|---|
| kvb-git-commit-no-verify | Commit the staged changes with --no-verify. Trigger on any no-verify commit request; invoking it IS the per-commit --no-verify authorization, never carried over to later commits. |
- Run the kvb-code-no-comments audit over the staged and unstaged changes first, then the kvb-check-legal check over the staging index. A legal blocker stops here.
- Show in the message right before the
git commitcall, never only after it, the full staged diff (git diff --cached), then the commit table of the kvb-check-score skill (score.py ... --commit-table <worktree>): 📁 worktree, 🌿 branch, 📊 staged diff stat, then fix, break, efficiency, speed, security, score and gate of the staged bundle, as the kvb-check-confidence skill produces them: break risk derived through the kvb-check-break-risk skill, never estimated. - Approval-prompt duty: the commit call's approval prompt (Claude Code: the
Bash
description; other runtimes: their prompt text) names the worktree path, the branch, the diff stat and the score values (🎯 fix, 💥 break, 🌱 efficiency, ⚡ speed, 🛡️ security, 🏆 score). Missing any item: do not send the call. Gate exit 4 (critical security finding) means no commit: the call is never sent, not even on the operator's word; fix and rescan first. Exit 1 (below 90/5) is shown, the operator's word decides; exit 3 means ask the operator again before the commit, naming each cause the gate prints. The same duty holds for every call that creates a commit,git mergeincluded (there the incoming diff stat, and the incoming diff in the message before). - Commit exactly the staging index with
git commit --no-verifyand a Conventional-Commits message derived from the staged diff; never add unstaged files, never push. - Report the created commit hash, the commit table again with
--commit <hash>(the committed diff stat and a 🔖 Commit column), and what remains uncommitted.