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>
3.9 KiB
3.9 KiB
name, description
| name | description |
|---|---|
| kvb-check-principles | Find violated principles (SPOT, DRY, KISS, SRP, trust boundaries) in a repository, path or diff. Trigger on "sei skeptisch", "kritische analyse", or "review the architecture". |
The stance is adversarial: the code is guilty until its structure proves
otherwise. This skill hunts violated principles, not bugs (code-review),
bloat (ponytail-audit) or leaked secrets (kvb-check-security). Read-only:
report, change nothing unless the operator asks afterwards.
Scope
The operator names the target: a repository, directory, role or diff. Without one, take the whole repository and rank by blast radius. State the scope in one line and name what you did not read; a silent half-audit reads as clean.
The lenses
Apply each independently; a finding belongs to exactly one:
- SPOT: one truth, one place. A value, version, hostname, schema or list of names that exists twice will diverge. Name both locations and the drift.
- DRY: repeated knowledge, not text. Look-alike blocks that change for different reasons are correctly separate; merging them is the violation. Prove the shared reason to change, or drop the finding.
- SRP: one reason to change per unit: the module that parses and persists, the function named "x and y", the role that configures, deploys and monitors. Name the two stakeholders who would each demand a change.
- KISS: mechanism nobody asked for: an abstraction with one implementation, a config value that never varies, a cache with no measured pressure, a retry loop around a deterministic call.
- Security, only at trust boundaries: unvalidated input reaching a query, shell, template or path; authorization checked in the caller instead of the resource; a secret in a default, log or image layer; a permission wider than the operation needs. Defensive findings only.
- Silent defaults: a fallback substituting a guess for a value the
caller failed to supply, turning a misconfiguration into wrong behaviour
instead of a loud failure (the
kvb-code-no-defaultsskill).
Method
- Graph first: explore through the codebase-memory-mcp graph
(
search_graph,trace_path,get_architecture,detect_changes; thekvb-agent-optimizeskill sets it up), grep and read after. - Evidence before verdict: every finding carries a
file:lineyou read. Grep the sibling occurrences before calling something a duplicate; one hit is not a pattern. - Name the failure: which value drifts, which caller breaks, which input reaches which sink. A finding whose worst case is "feels wrong" is deleted, not softened.
- Attack your own finding: run anything consequential or expensive to fix
through the
kvb-think-dialecticskill before reporting it; the strongest counter is usually "not the same knowledge" or "already checked upstream". Skeptics scale with the stakes; each brief names thefile:lineand the claim and caps the answer at five lines. - Respect intent: a deliberate marker (
ponytail:, a documented exception, a nocheck directive with a reason) is a known ceiling, a finding only once exceeded.
Output
One table, worst blast radius first:
| Severity | Principle | Location | What is wrong | Smallest fix |
Then at most three lines: what the scope excluded, which findings survived
kvb-think-dialectic and which are still derived-only, and the one to fix
first. No per-finding paragraphs; the operator asks when a row needs it.
Rules
- Never report formatting, naming taste or missing comments.
- Mark each finding proven (grepped, read, reproduced) or derived (reasoned
statically), and close with the
kvb-check-confidenceskill's numbers for the audit. - No silent caps: if you ranked and cut, say how many findings were dropped and by what rule.
- Skepticism ends at the report: no fix, stage or refactor in this skill.