OpenClaw

new-tag

Prepare and publish a git release tag by inspecting the repo's release convention, bumping affected package versions, validating release builds, committing the release prep, pushing the branch, and pushing a new tag. Use when asked to bump project versions, cut a release, push a tag, or trigger tag-based GitHub Actions or npm publishing.

femto0 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install femto/new-tag

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

New Tag

Workflow

Inspect the release convention

Check git status --short, the current branch, and recent tags before changing versions.
Inspect .github/workflows/ for tag patterns such as v*, package filters, build jobs, and publish jobs.
Inspect package manifests and release scripts to determine which package version should drive the new tag.

Choose the version plan

Follow the repository's existing tag pattern unless the user explicitly wants to change it.
Bump only the packages affected by the release.
Bump shared packages when their changed code is consumed by a package that will be published from this tag.
Keep compatibility gates unchanged unless the new release actually requires a higher minimum version.
If the worktree contains unrelated changes, stop and ask before including them in the release.

Apply the version changes

Update package versions in manifest files.
Update release workflows, workspace filters, and package references when package names or published artifacts have changed.
Fix any packaging or TypeScript resolution issues discovered while preparing the release.

Validate before tagging

Run the builds required by the release workflow, not just a subset that happens to pass locally.
At minimum, build every package that the tag-triggered workflow will build or publish.
Do not create or push a tag while any required build is failing.

Commit and push the release prep

Stage only the files that belong in the release prep.
Use a clear release-oriented commit message such as Prepare vX.Y.Z release.
Push the branch before creating the tag so the tag points at a commit already on the remote.

Create and push the tag

Create an annotated tag that matches the workflow trigger, usually vX.Y.Z.
Push the tag explicitly.
Report the commit SHA, tag name, and any workflows that should now trigger.

Command Pattern

Use this sequence as the default pattern and adapt it to the...

来源信息

Source: github
Repository: openclaw/skills
Path: skills/femto/new-tag
Version: —
Commit: 88e5eaeb0326a9b45501bc2c8c1b1503b303ce00
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# New Tag

## Workflow

### Inspect the release convention

- Check `git status --short`, the current branch, and recent tags before changing versions.
- Inspect `.github/workflows/` for tag patterns such as `v*`, package filters, build jobs, and publish jobs.
- Inspect package manifests and release scripts to determine which package version should drive the new tag.

### Choose the version plan

- Follow the repository's existing tag pattern unless the user explicitly wants to change it.
- Bump only the packages affected by the release.
- Bump shared packages when their changed code is consumed by a package that will be published from this tag.
- Keep compatibility gates unchanged unless the new release actually requires a higher minimum version.
- If the worktree contains unrelated changes, stop and ask before including them in the release.

### Apply the version changes

- Update package versions in manifest files.
- Update release workflows, workspace filters, and package references when package names or published artifacts have changed.
- Fix any packaging or TypeScript resolution issues discovered while preparing the release.

### Validate before tagging

- Run the builds required by the release workflow, not just a subset that happens to pass locally.
- At minimum, build every package that the tag-triggered workflow will build or publish.
- Do not create or push a tag while any required build is failing.

### Commit and push the release prep

- Stage only the files that belong in the release prep.
- Use a clear release-oriented commit message such as `Prepare vX.Y.Z release`.
- Push the branch before creating the tag so the tag points at a commit already on the remote.

### Create and push the tag

- Create an annotated tag that matches the workflow trigger, usually `vX.Y.Z`.
- Push the tag explicitly.
- Report the commit SHA, tag name, and any workflows that should now trigger.

## Command Pattern

Use this sequence as the default pattern and adapt it to the...

搜索