busic-version-management
SkillFiles & storageBuSic version number management specification. Used to verify SemVer format, version change levels, the source-of-truth version file, and version-related data that must be synchronized before release.
Use busic-version-management in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add busic-version-management and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the busic-version-management skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
What this skill tells your AI
The instructions your AI receives, as published by glowled/busic in .agents/skills/busic-version-management/SKILL.md and read by Ahel’s review.
何时使用
- 要判断这次改动应该升
major、minor还是patch - 准备发布版本，需要知道哪些文件必须一起改
- 想确认应用内更新、Git tag、用户可见版本之间的关系
先看这些真源
docs/20-workflows/release-workflow.mddocs/10-project/update-system.mddocs/30-reference/source-of-truth.mdpubspec.yamlversions-manifest.jsonCHANGELOG.md
版本格式
BuSic 使用：
major.minor.patch+build
规则：
major：不兼容变更minor：向后兼容的新功能patch：向后兼容的修复或小优化build：构建序号，只在内部流转和发布资产中使用
用户可见版本与 Git tag 不带 +build，示例：
pubspec.yaml：1.2.3+45- 用户可见：
1.2.3 - Git tag：
v1.2.3
发布时必须同步的文件
pubspec.yaml：真实版本号CHANGELOG.md：面向人的变更记录versions-manifest.json：应用内更新主真源
如果是正式发布，还要同步确认：
何时升哪个版本
- 有破坏性协议、迁移或接口调整：升
major - 有新功能但兼容旧行为：升
minor - 只是修复、稳定性改善、非破坏性优化：升
patch
如果一次改动同时包含新功能和修复，通常按最高级别处理。
容易漏掉的点
- 只改了
pubspec.yaml，没改versions-manifest.json - 改了 Release 资产名，但忘了同步更新应用内匹配逻辑
- 只看 GitHub Releases 页面，没检查 manifest 是否已更新
- 在 skill 里硬编码“当前最新版本号”这种容易过时的信息
相关 Skill
Signals
- GitHub stars
- 27
- Forks
- 8
- Last commit
- Sep 2026
Advanced
- Item type
- skill
- Key
busic-version-management- Source
- github.com/glowled/busic