Files
skills/skills/kvb-cleanup/docker.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

1.5 KiB

Docker items

Inventory

docker system df -v; containers with state and compose project label, volumes with the containers using them (docker ps -a --filter volume=<name>), dangling and unused images, build cache, unused networks. For every stopped container (exited, created) record its volumes ({{.Mounts}}); for every volume no running container uses, record size, CreatedAt (docker volume inspect) and compose project label, anonymous ones included.

Volumes checklist

Stopped containers and volumes always get their own checklist (multiSelect: true, header ⚠ Volumes, in a further call when call 1 is full). Every stopped container and every volume without a running container appears there unless a peer claimed it; none is dropped as "not proposed", unknown and anonymous ones included. The question text carries the warning: Deleting a volume is irreversible; its data does not come back unless the description says how. One option per stopped container together with its volumes (removing the container alone frees nothing of them), one per unattached volume, anonymous ones grouped. Each description gives size, CreatedAt, owner or compose project, and what is lost.

After removing images

Locally built images free little on their own: their layers stay behind as build cache. Re-measure docker system df; the layers show up as reclaimable build cache. Offer docker builder prune --filter until=24h as a follow-up candidate, ask the peers that claimed build cache first, and run it outside their running builds.