github rebelytics/one-skill-to-rule-them-all v3.12.0
v3.12.0: test-line merge, a 600-line core and a session-start log

one hour ago

This release merges the release/v3.12.0 test line after one test week. Most of its changes were exercised during that week or checked with a fixture. Seven were not exercised and ship untested, and two were exercised and do not hold yet; both groups are named below.

What changes for you

The core SKILL.md is re-split by episode to 600 lines. The rules that fire every session stay in it, and the detail of each episode (the bridged scan, staged-work reconciliation, archival, field edits, the quick reference) lives in the reference file that owns it, loaded when that episode starts. Every reference file declares its line ceiling, and the bundle validator refuses a release whose core grows past 600.

The session-start checklist is written to skill-observations/session-starts.log instead of the first reply, which carries only an item that failed or needs you.

The version and the core ceiling move under metadata (metadata.version, metadata.core_max_lines), and the validator checks the top-level frontmatter keys against the Agent Skills set.

Reviews say more about themselves: the scan prints the age of the last review and how many open entries were never reviewed, a review record carries its yield for the period and a line for each rule it removed, and the repeated-error rate is measured from the log before any comparison of two versions.

Smaller fixes, each with its reporter credited: the starter-set marker format is stated and read strictly; the scan's suspect-YAML note names each file; the full scan invocation is shown with --entries-to before the root; the hook and the sibling probe count open entries the way the review does; each found log is resolved before the sibling-log dedup; the starter-set import is read back before the marker is written; the skill card is an install route where the harness makes it the only one; the first batch is ordered for a host that requires its plan call first; a disk load counts as activation when the listing omits an installed skill; the post-compaction note no longer reads as cancelling the protocol; the first batch is named in the activation block and a missing mount is asked for and re-probed; completions are counted in any host plan tool; a staged barrier names the tests it needs; the staging manifest gains a depends_on_unverified field; a claimed gap is checked at its target; and the core re-split asked for in #176 is done.

Shipped untested

These seven changes were not exercised during the test week. They ship as written, checked by a read-through or a fixture of the mechanism, not by use: the bridged scan writing its entries to a file by default; an unfilled pin reported as an unfinished install (#393); the per-skill lookup in the hook's first batch and at slash-command loads (#415); the activation block's one-line summary wording, whose check is a re-audit after the release; the bounded review slice's own entry file (#416); staged work left under a previous workspace root (#230); and findings read from declared feedback channels at review Step 1 (#220). If one of them does not behave as described in your setup, please open an issue or reopen the one it closed.

Not holding yet

Two changes were exercised and did not hold in use: a subagent hand-back as a checkpoint trigger (#409), and the review's check that each session left its items 4-5 line. The fix for both is on the release/v3.13.0 test line: the call that records a delegate's return writes the checkpoint line itself, and the scan pairs the session-start lines per session label. It ships when that line merges, and #409 stays open until then.

Thanks to everyone who reported, measured and tested: @AceAchillez, @akjenkins2, @batuhanocal, @BBS-Comunicaciones, @benjaminearlevans, @Daniel129418, @decofc, @dispather, @ghenderson712, @golfxpy, @guedesaraujomarketing-ux, @lVerityl, @maneirag-prog, @maushdev, @Memnoch9178, @minorum, @osilvaarthur, @petqa, @QuasiGrant, @rnafulh-wq, @TarvisWK and @ZepiGit.

Full list of changes: the commit history from v3.11.0 to v3.12.0.

Don't miss a new one-skill-to-rule-them-all release

NewReleases is sending notifications on new releases.