Skip to content

The skill version stamp fell three bumps behind its own frontmatter - #177

Merged
anilcancakir merged 1 commit into
masterfrom
fix/skill-version-stamp
Sep 20, 2026
Merged

anilcancakir merged 1 commit into
masterfrom
fix/skill-version-stamp

Conversation

@anilcancakir

Copy link
Copy Markdown
Member

SKILL.md's stamp comment read Skill v0.1.31 (2026-09-19) while its frontmatter read version: 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.14 release (f086c0c) both read 0.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.

…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.
@kodizm

kodizm Bot commented Sep 20, 2026

Copy link
Copy Markdown

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 magic 0.0.14 | Skill v0.1.34 (2026-09-20) agrees with the frontmatter version: 0.1.34 on line 5, with pubspec.yaml's version: 0.0.14, and with today's date. grep confirms the stamp and the frontmatter are the only two places in the repo carrying a skill version, so there is no third copy left behind.

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 — Url() appears in references/forms-validation.md (and in eloquent-orm.md / routing-navigation.md). So v0.1.34 is not asserting verification against content the skill does not actually cover.

No CHANGELOG entry is required here: CLAUDE.md's post-change sync is scoped to code changes under lib/, and this touches neither.

Tests

None, and none are warranted — the change is a single HTML comment in a Markdown file with no executable surface.

Checks I ran

  • read_pull_request_diff (manifest + patch): 1 file, +1/-1, nothing changed_without_diff or dropped_for_size.
  • grep -rn "Skill v0.1." and grep -rn "0.1.3[0-9]" skills/ doc/ .github/: only SKILL.md:5 and SKILL.md:8 — no other stale copy.
  • grep -m1 '^version:' pubspec.yamlversion: 0.0.14, matching the magic 0.0.14 half of the stamp.
  • dart format --set-exit-if-changed skills/Formatted no files, exit=0.
  • I did not run flutter test or dart analyze: no Dart file changed, so neither could observe this diff.

@anilcancakir
anilcancakir merged commit 3c1fc4b into master Sep 20, 2026
3 checks passed
@codecov

codecov Bot commented Sep 20, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant