Files
skills/skills/kvb-ci-triage/stale-run.md
T
Kevin Veen-BirkenbachandClaude Opus 5.5 3c2f6c44b5 refactor(skills): cap every SKILL.md at 600 words and cut agent messages
Every loaded SKILL.md and every listed description is paid on every turn of every session, and every delivered message costs its recipient a full turn. scripts/budget.py gains SKILL_WORDS = 600, enforced by test_lock, and test_naming forbids a skill naming its own slash command; 53 descriptions and 10 body lines drop it. The 18 longest skills move details into 31 side files read only in their situation (organize's capacity, succession, peers, offices, relay and lineage; cleanup's docker, worktrees, execute and ask; code-tune, changelog, triage, dream, split and others), so all SKILL.md files shrink from 33866 to 26291 words without dropping a rule; an independent review of HEAD against the new text found no loss in 60 of 64 skills and three weakenings, now restored (WSJF re-estimates after an objective change, cleanup's volume checklist, essence's absolute dates).

The kvb-org-organize Peer protocol sends status that asks nothing to the news board, answers nothing that asks nothing, keeps messages terse, and lets light runs admit themselves in the operator's wording; the skills follow it (operator reads the register, relax and wakeup reply through the news, evening collects them there, wsjf asks only for missing estimates, cleanup and triage batch their questions). Skills that explore code ask the codebase-memory-mcp graph first, subagent briefs scale with the stakes and cap their answers, and the skills that need the full register or council tables call show --wide or list --long.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-04 17:07:23 +01:00

791 B

Run behind HEAD

A CI run is a snapshot of one commit, and the branch has moved since. Scope the job set down before enumerating, clustering or spawning anything: every job investigated against stale code is work thrown away, and a fix proposed there risks reverting someone else's.

Two cheap discriminators, without opening an artifact:

  • git diff --name-only <run-sha>..HEAD -- <source dir> | cut -d/ -f2 | sort -u shows which components already moved.
  • A grep of the saved job logs for the literal error signature of each cause already fixed in that range.

What survives both is the job set the procedure applies to; say how many jobs you dropped and why. The run cannot contain a fix that landed after it, so looking only at its commit can only ever confirm the failure.