‹ 首页

dot-ai-tag-release

@vfarcic · 收录于 1 周前 · 上游提交 1 周前

Create a release tag based on accumulated changelog fragments. Run when ready to cut a release.

场景版本发布变更管理

适合你，如果每次发布前需要手动整理变更并打标签

/ 下载安装
https://github.com/vfarcic/dot-ai-cli/tree/main/.claude/skills/dot-ai-tag-release ↗
/ 通过 npx 安装 校验哈希
npx oh-my-skill add vfarcic/dot-ai-cli/dot-ai-tag-release
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- vfarcic/dot-ai-cli/dot-ai-tag-release
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify vfarcic/dot-ai-cli/dot-ai-tag-release
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
7GitHub stars
~466最小装载
~466含声明引用
~1.1K文本包总量
索引托管

怎么用

商店整理自技能原文 · 版本 af67e07 · 表述以原文为准
它做什么

装上后，Claude 会帮你分析变更日志片段，提议下一个语义版本号，创建并推送 Git 标签，最后确认标签已生成。

什么时候触发

当多个 PR 已合并并带有变更日志片段，且你准备发布新版本时，可以要求 Claude 执行此技能。

装好后可以这样说
技能原文 SKILL.md作者撰写 · MIT · af67e07

Create Release Tag

Create a semantic version tag based on accumulated changelog fragments.

When to Use

Run this skill when:

  • Multiple PRs have been merged with changelog fragments
  • You're ready to cut a release
  • After the /prd-done workflow completes (not during it)
Workflow
Step 1: Analyze

Run the analysis script bundled with this skill:

bash .claude/skills/dot-ai-tag-release/analyze.sh

If the script fails (non-zero exit) or the output contains ERROR=true, show the MESSAGE to the user and stop.

If the output contains NO_FRAGMENTS=true, inform the user there's nothing to release and stop.

Step 2: Propose Version

Present the script output to the user:

  1. Current version (CURRENT_VERSION)
  2. Fragments found (the FRAGMENTS list with their types)
  3. Proposed next version (PROPOSED_VERSION) based on bump type (BUMP_TYPE)
  4. Ask for confirmation or allow override
Step 3: Handle [skip ci]

If SKIP_CI=true, inform the user that tagging HEAD would prevent the release workflow from running. Create a preparation commit:

git commit --allow-empty -m "chore: prepare release [version]"
git push origin HEAD
Step 4: Create and Push Tag

After confirmation:

git tag -a [version] -m "[Brief description summarizing the fragments]"
git push origin [version]
Step 5: Confirm Success

Show the user:

  1. The tag created
  2. The tag URL on GitHub (if applicable)
  3. Note that CI/CD will generate release notes from the fragments
Guidelines
  • Don't run during PR workflow: This is a separate release activity
  • Review fragments first: Make sure all fragments are accurate before tagging
  • Use semantic versioning: Follow semver strictly based on fragment types
  • Brief tag message: Summarize the release in 1-2 sentences
  • Never tag [skip ci] commits: Always create a preparation commit first
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…