Efficiency and speed are after/before ratios where over 100 % is worse, so the labels now read 💸 cost and ⏱️ time in score.py, tokens.py, measure.py, the gate texts, the message block and every skill that quotes them; 💰 stays the value quotient and the --efficiency/--speed flags keep their names. --commit-table drops the worktree column, which took the table's width, and prints the path below it alone in a text block for copy and paste. 🎯 Fix: 94 % 💥 Break: 2 % 💸 Cost: 100 % ⏱️ Time: – 🛡️ Security: 100 % 💰 Value: ? 🏆 Score: 92 🚦 Gate: ✅ 90/5, cost and time <= 100, security 100 % Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.3 KiB
1.3 KiB
name, description
| name | description |
|---|---|
| kvb-check-speed | Wall-clock speed of changed code versus its base commit. |
Its ⏱️ time is the share of its base's wall-clock time a change needs:
under 100 % it is faster, over 100 % slower. It has no script of its own: one run
of the kvb-check-efficiency measurement yields both values.
python3 ${CLAUDE_SKILL_DIR}/../kvb-check-efficiency/scripts/measure.py --base <ref> -- <command...>
Its ⏱️ time <p> % (wall <b>→<a> s) compares wall seconds at <ref> and
in the working tree: one run each, or the mean of 5 each when a value
exceeds 100. The command, the runs, the queue.py hold wrapper for heavy
commands and the exit codes are those of the kvb-check-efficiency skill;
pasting its whole line reports both values at once.
- Skills have no speed: only their tokens count. Pass
--speed -tokvb-check-score, which shows–. - Code without a runnable path (configuration, templates no command
renders) has no speed either:
--speed -, and say why. - Other load: wall time follows host load. Above 30 % other load the
script falls back to the CPU-time ratio and marks the estimate:
⏱️ time ~<p> % (cpu <b>→<a> s), ending in(estimated: other load <x> %). Report the run you made; never rerun to pick the best result.