skill: fold the spool — section 596 gets its number on master - #3344
Merged
Conversation
Refs #3236 The first `tri skill fold` ever run from master. One spooled lesson became section 596, numbered against SKILL.md as it stands at this moment, and its spool file was deleted in the same commit. The diff is the point: .claude/skills/ci-gates/SKILL.md | 46 ++++++++++++++++++++++ incoming/2026-09-05-i-said-master-was-green-...md | deleted 46 insertions, ZERO deletions in SKILL.md, and one spool file removed. That one-section-per-spool-file shape is what makes a fold distinguishable from a direct append in a branch diff, and it is the whole reason the number can be assigned here rather than on a feature branch: this runs once, on one branch, with the file in front of it, so two branches cannot pick the same number. The lesson folded is the one about reporting "master is green" after reading two of sixty-three workflows -- 40 success, 11 failure, 12 never ran, with `Issue Gate` among the eleven and supplying one of the four required contexts. `tri skill check` 554 -> 555 sections, exit 0. `tri skill refs` exit 0. Five more lessons are spooled in #3327 and will fold after that merges.
gHashTag
enabled auto-merge (squash)
September 6, 2026 02:20
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #3236
The first
tri skill foldever run from master. One spooled lesson becamesection 596, numbered against SKILL.md as it stands at this moment, and its
spool file was deleted in the same commit.
The diff is the point
46 insertions, zero deletions in SKILL.md, and one spool file removed. That
one-section-per-spool-file shape is what makes a fold distinguishable from a
direct append in a branch diff — and it is the whole reason the number can be
assigned here rather than on a feature branch. This runs once, on one branch,
with the file in front of it, so two branches cannot pick the same number.
That was the defect: two branches each appending
## N.numbered from their ownbase, both merging, the number appearing twice — twice in two passes, after which
the two repairs collided with each other as well.
What folded
Section 596, the lesson about reporting "master is green" after reading two of
sixty-three workflows. Measured properly: 40 success, 11 failure, 12 never
ran — and among the eleven was
Issue Gate, which suppliescheck-linked-issue,one of the four contexts required to merge.
tri skill check554 → 555 sections, exit 0 ·tri skill refsexit 0.Five more lessons are spooled in #3327 and fold after that merges.