Veraltete Skill-Aufzaehlungen in der Instruction-Schicht nachgezogen (#129, #130)
CI / verify (push) Successful in 48s
Release / release (push) Successful in 38s

Files changed:
- CHANGES.md
- VERSION
- instructions/CONTRACT.md
- instructions/bootstrap.md
- instructions/dev/stack-close/SKILL.md
- instructions/dev/stack-dev/SKILL.md
- tools/chemenu/tests/test_instructions_cmd.py
This commit is contained in:
torben committed 2026-09-20 11:52:02 +02:00
1 parent 52ba5ba768
commit 3c1d4cb028
7 files changed
+51 -16

No files matched your search

+10 -7
View File
@@ -244,9 +244,9 @@ than the source, and without the sibling files a relative link might expect. A m
correct at `instructions/<name>/SKILL.md` (`../session-setup.md`, `../../kb/CONTRACT.md`)
resolves to a different, usually nonexistent, file once copied: the number of `../` segments
that reaches a target from `instructions/` does not reach the same target from
`.claude/skills/`. Fifty-two of the fifty-eight relative links across this repo's seven skills
broke exactly this way before this rule existed, silently - nothing rendered the copy to notice,
and no check read a link target.
`.claude/skills/`. Fifty-two of the fifty-eight relative links across the repo's seven skills at
the time broke exactly this way before this rule existed, silently - nothing rendered the copy to
notice, and no check read a link target.
So a `SKILL.md` never writes an outbound reference as a relative markdown link, correct depth or
not. It names the target as a repo-root-relative **plain path** instead - `` `instructions/session-setup.md` ``, not `[session-setup.md](../session-setup.md)`; `` `kb/CONTRACT.md` `` for a
@@ -320,7 +320,7 @@ marker: the pointer is worth having in the origin repo and resolves nowhere else
Anthropic's skill-authoring guidance suggests, for a "particularly complex workflow", a checklist
the agent copies into its response and ticks off as it goes. It names no threshold, so this repo
sets one - otherwise the two skills that have such a block and the three that do not read as an
sets one - otherwise the skills that carry such a block and the ones that do not read as an
accident rather than a decision.
A `SKILL.md` carries the block when **one** of its flows runs to eight steps or more *and* that
@@ -332,9 +332,12 @@ because the next call fails without the previous one.
Two skills qualify today, and the block names each of their numbered steps once, verbatim:
`wiki-ingest` (twelve steps, of which `## Not Extracted` in step 6, the coverage check in step 10
and the lint cadence in step 12 all fail quietly) and `wiki-lint` (nine, with steps 3-6 pure
judgment). The other three do not, and the reason is worth stating so nobody adds one out of
symmetry: `wiki-manage` has two flows of seven, `wiki-query` six, `wiki-status` five, and none of
them is long enough for a reader to lose the thread.
judgment). The rest do not, and the reason is worth stating so nobody adds one out of symmetry:
`wiki-manage` has two flows of seven, `wiki-query` seven, `wiki-status` five and
`gtd-weekly-review` five - none of them long enough for a reader to lose the thread.
<!-- dist:strip-start -->
Dev-instance-only: `stack-dev` (six) and `stack-close` (four) sit under the same threshold.
<!-- dist:strip-end -->
The block says that it is to be copied and carried, not read. A checklist read once is the table
of contents it replaced.