ci-gates skill: the section that named the pattern committed it (Refs #2161) - #2661
Merged
Conversation
…2161) `tri pointers` shipped, and its first run on master flagged §120 -- the section documenting it -- because that section quoted the dead path after a cue word while explaining the bug. 16 -> 17, and the row named the skill file. Third instance in one session, after the equivalence marker and the pointer tool's own docstring. The trigger lives in the vocabulary, so every document that teaches the vocabulary carries it; the durable defence is to run the checker after writing about the checker and read the count. Fixed the writer, not the tool, as the rule chosen one commit earlier requires: a special case for skill files would blind the checker to exactly the documents most likely to discuss paths.
Contributor
PR DashboardGenerated at: 2026-08-24 04:05:32 UTC
Summary
Seal Status
|
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
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.
tri pointersshipped, and its first run on master flagged §120 — the section that documents it. That section quoted the dead path after a cue word while explaining the bug. The count went 16 → 17 and the row named the skill file.Third instance in one session, after the equivalence marker (§118) and the pointer tool's own docstring (§120). This one is the sharpest: the section that names the pattern, warns you to expect it, and prescribes fixing the writer rather than the tool — committed the pattern in the act of describing it, and was caught by the check it was documenting.
The honest form of the lesson: this is not a mistake you make once and then know better. The trigger lives in the vocabulary, so every document that teaches the vocabulary carries it. The only durable defence is the one that caught all three — run the checker after writing about the checker, and read the count.
Fixed the writer, not the tool, as the rule chosen one commit earlier requires. A special case for skill files would blind the checker to exactly the documents most likely to discuss paths.
Refs #2161