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>
This commit is contained in:
1 parent
34b434a744
commit
3c2f6c44b5
99 files changed
+2110
-2086
No files matched your search
@@ -2,38 +2,38 @@
|
||||
name: kvb-git-commit-next
|
||||
description: >
|
||||
Search every branch for the staged fix, commit it with --no-verify, then
|
||||
stage and brief the next bundle. Trigger on /kvb-git-commit-next or a
|
||||
request to commit and stage next.
|
||||
stage and brief the next bundle. Trigger on a request to commit and stage
|
||||
next.
|
||||
---
|
||||
|
||||
1. `git fetch --all --prune --tags`, then hunt the staged fix across every
|
||||
ref with the kvb-git-merge-fix skill's `find_fix.py` (by `--grep`, by `-S`, by
|
||||
`--path`). Describe the staged bundle in one line first so a
|
||||
wrong search intent is visible. Only the search runs here — never
|
||||
cherry-pick or merge, and never touch the staging index or the tree.
|
||||
2. A similar fix on another branch is a stop: run the kvb-think-dialectic skill on the
|
||||
two candidates (staged version as thesis, foreign commit as antithesis)
|
||||
until one survives, then present sha, branch, both diffs, the verdict and
|
||||
the recommended move (keep staged / take theirs / combine). Wait for the
|
||||
operator's decision; do not commit.
|
||||
1. Describe the staged bundle in one line, so a wrong search intent is
|
||||
visible. Then `git fetch --all --prune --tags` and hunt the staged fix
|
||||
across every ref with the kvb-git-merge-fix skill's `find_fix.py` (by
|
||||
`--grep`, by `-S`, by `--path`). Only the search runs here: never
|
||||
cherry-pick or merge, never touch the staging index or the tree.
|
||||
2. A similar fix on another branch is a stop: run the kvb-think-dialectic
|
||||
skill on the two candidates (staged version as thesis, foreign commit as
|
||||
antithesis) until one survives, then present sha, branch, both diffs, the
|
||||
verdict and the recommended move (keep staged / take theirs / combine).
|
||||
Wait for the operator's decision; do not commit.
|
||||
3. Nothing similar found, or the operator picked the staged version: run the
|
||||
kvb-git-commit-no-verify skill on the currently staged changes (kvb-code-no-comments
|
||||
audit and kvb-check-legal check first, then its four-line block of
|
||||
worktree path, branch, fix confidence and break risk, then
|
||||
`git commit --no-verify`, exact staging index only).
|
||||
4. Group the remaining uncommitted changes into logical bundles (one
|
||||
concern per bundle: same failure class, same mechanism, or same role)
|
||||
and stage the next one; never mix concerns to save a commit. Staging
|
||||
happens here and nowhere else: never stage merely to run a lint or a
|
||||
test. Repository checks that enumerate through `git ls-files` already
|
||||
see tracked, modified files and read the worktree; only an untracked
|
||||
NEW file needs `git add` to become visible. Path-scope every `git add`
|
||||
to the bundle — `git add -A` sweeps up the operator's own edits and
|
||||
their local config. A file that carries two bundles is staged by line:
|
||||
`${CLAUDE_SKILL_DIR}/scripts/stage_hunks.py --repo <worktree> --file
|
||||
<path> --match <regex>`, first with `--dry-run`.
|
||||
5. For the newly staged bundle run the kvb-think-explain skill (what the changes do
|
||||
and how the pieces interact, file:line-anchored) followed by the
|
||||
kvb-check-confidence skill (fix confidence, break risk, evidence, residuals).
|
||||
kvb-git-commit-no-verify skill on the currently staged changes
|
||||
(kvb-code-no-comments audit and kvb-check-legal check first, then its
|
||||
four-line block of worktree path, branch, fix confidence and break risk,
|
||||
then `git commit --no-verify`, exact staging index only).
|
||||
4. Group the remaining uncommitted changes into logical bundles (one concern
|
||||
per bundle: same failure class, mechanism or role) and stage the next one;
|
||||
never mix concerns to save a commit. Staging happens here and nowhere
|
||||
else: never stage merely to run a lint or a test. Checks that enumerate
|
||||
through `git ls-files` already see tracked, modified files and read the
|
||||
worktree; only an untracked NEW file needs `git add` to become visible.
|
||||
Path-scope every `git add` to the bundle: `git add -A` sweeps up the
|
||||
operator's own edits and local config. A file that carries two bundles is
|
||||
staged by line: `${CLAUDE_SKILL_DIR}/scripts/stage_hunks.py --repo
|
||||
<worktree> --file <path> --match <regex>`, first with `--dry-run`.
|
||||
5. For the newly staged bundle run the kvb-think-explain skill (what the
|
||||
changes do and how the pieces interact, file:line-anchored), then the
|
||||
kvb-check-confidence skill (fix confidence, break risk, evidence,
|
||||
residuals).
|
||||
6. Close with what remains unstaged and wait for the operator's commit
|
||||
decision; never auto-commit the newly staged bundle.
|
||||
Reference in new issue
Block a user