Semver and version sync
Skill swd3k/skills/agent-skills/programming/semver-and-version-sync
Portable agent skills for desktop apps, programming, UI, and web design - Codex, Claude, Cursor, Grok. English SKILL.md playbooks (Photino, Inno, CI, landings).
npx -y skills add swd3k/skills --skill semver-and-version-syncAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 18 days oldThe repository was created 18 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Keep product version consistent across assembly, UI, installer, updater, and git tags. Use when versions drift, release notes mismatch, or auto-update compares wrong strings.
SKILL.md
1.0 KB, as published. Nobody here has run it
SemVer and Version Sync
Single source of truth
Pick one:
Directory.Build.props<Version>- Or tag-only (CI injects) — then local dev shows
0.0.0-dev
Surfaces that must match
- Assembly / InformationalVersion
- UI footer ("v2.0.2")
- Inno
MyAppVersion - Updater comparison baseline
- Git tag
vMAJOR.MINOR.PATCH - CHANGELOG section header
Release workflow
- Bump version in props
- Update CHANGELOG
- Commit
release: X.Y.Z — short reason - Tag
vX.Y.Zand push tags - Verify Release assets sizes and notes
Pitfalls
- UI hardcodes 2.0.2 while props still 2.0.1
- Tag on wrong commit after amend/rebase
- Prerelease tags without clear channel
Acceptance
- Grep for old version finds nothing relevant
- Updater considers equal versions "up to date"