The skill version stamp fell three bumps behind its own frontmatter - #177
Conversation
…atter The stamp comment said Skill v0.1.31 while the frontmatter said 0.1.34. The review that spotted it called the drift pre-existing; it is not. At the 0.0.14 release both read 0.1.31, and the three bumps that opened the gap are mine: #174, #176 and #175 each raised the frontmatter and left the comment alone. The stamp is what a reader checks to see whether the skill was verified against the current API surface, so one that lags by three revisions says the opposite of what it is for.
|
Note Kodizm (AI-generated). May contain mistakes; verify before acting. One-line stamp correction that is internally consistent with every version it references — nothing to flag. The new stamp I also checked that the claim the stamp makes is substantively true rather than just numerically aligned: the API surface added in the bumps that opened the gap is present in the skill body — No CHANGELOG entry is required here: TestsNone, and none are warranted — the change is a single HTML comment in a Markdown file with no executable surface. Checks I ran
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
SKILL.md's stamp comment readSkill v0.1.31 (2026-09-19)while its frontmatter readversion: 0.1.34.The review that spotted it in #175 called the drift pre-existing. It is not, and I want that on the record: at the
0.0.14release (f086c0c) both read0.1.31. The three bumps that opened the gap are mine, one per PR: #174, #176 and #175 each raised the frontmatter and left the comment alone.The stamp is what a reader checks to see whether the skill was verified against the current API surface. One that lags by three revisions says the opposite of what it exists to say.
Docs only, one line.