fix(docs): skill entrypoints belong to check-skills, not the band cap #1110
No reviewers
Labels
No labels
burndown-2026-06
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agentic-os!1110
Loading…
Reference in a new issue
No description provided.
Delete branch "aos/claude/aw85-skill-size-owner"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #1109. Unblocks four repos on coilysiren/inbox#374.
Two hooks in one suite disagreed about the same file.
documentation-layoutapplied the band's per-file cap toSKILL.mdandCOMPOSED.md(40 lines / 3,000 chars on small) whilecheck-skillsallows 500 lines / 10,000 bytes for those same files fromcategories.yaml.The failure a skill got was also the wrong instruction:
A skill overflows into its own
references/, whichcheck-skillsleaves uncapped on purpose.Scope of the exemption
The two entrypoint basenames only. Every other Markdown file under a skill directory still takes the band cap, and the test asserts an ordinary doc of the same size still fails, so this is not a hole in the check.
Why it matters now
Measuring the fleet for the band migration found 56 skill files in this state across 23 repos, and it was the dominant burden in four repos whose
docs/were already clean: agentic-os-kai (73 non-docs files), deploy (42), agentic-os-xxx (34), agentic-os-hardware (15). Their issues told them not to start that part pending this decision.Verification
Mutation: removing the two basenames fails
test_skill_entrypoints_take_no_size_cap_from_this_hook.pre-commit run --all-filesclean, 540 tests green.