Kevin Veen-BirkenbachandClaude Opus 5.5
3c2f6c44b5
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>
863 B
863 B
Refactor: no test covers the change set
- Testable logic: write characterization tests first, against the current behaviour, including the behaviour you consider wrong, so the refactor cannot silently change it. Keep them small and framework-free unless the project already has a framework. Fix the captured wrongness in a separate change, never in this one.
- Not sensibly testable: pure glue, declarative config, a thin wrapper over a service the test would have to mock into meaninglessness, or a project with no test setup at all. Say so in one line and refactor without a net; do not invent a test harness the project never asked for.
The new tests are part of the deliverable and must still pass unchanged after the refactor. A test that had to be edited to stay green means the behaviour moved: revert the refactor, not the test.