release

Automate end-to-end version release workflows with X.Y.Z validation, testing, and tagging.

84|5|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/fitlab-ai/agent-infra --skill release-fitlab-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/fitlab-ai/agent-infra/tree/main/.agents/skills/release
Command: npx skills add https://github.com/fitlab-ai/agent-infra --skill release-fitlab-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

在软件开发工作流中,版本发布往往需要重复、繁琐且易出错的步骤。本 Skill 提供一个自包含的工作流,自动执行从版本格式验证到发布产物更新、测试校验、提交与打标签、以及里程碑管理的一整套版本发布流程,确保发布的一致性与可追踪性。

Core Features & Use Cases

  • 自动解析并验证版本号 X.Y.Z,确保格式正确且可回溯。
  • 检查工作区是否干净,避免未提交变更影响发布。
  • 在 main 分支下执行前置验证(git branch --show-current、npm test),并对非 main 分支给出警告但继续执行。
  • 更新相关引用(如 package.json、.agents/.airc.json 等)中的版本信息,确保各处一致。
  • 重建内联产物(build-inline.js),并将产物同步回工作副本。
  • 创建发布提交与标签,并管理里程碑以对齐后续发布计划。
  • 提供可重复的、可回滚的发布流程,降低人工干预风险。

Quick Start

在需要发布新版本时,输入目标版本号 X.Y.Z 即可触发完整发布流程并按步骤执行。

Frequently Asked Questions about release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate npm version releases end-to-end?

Automating npm version releases involves parsing a target X.Y.Z version, updating package.json references, running npm test, and creating release commits with tags to ensure synchronized versioning across artifacts.

What is the standard git workflow for synchronizing version updates across package files?

Synchronizing version updates across package files requires updating references like package.json and security docs, rebuilding inline artifacts, and generating a release commit with a corresponding tag on the main branch.

How do I manage release milestones after validating a new version?

Managing release milestones after validating a new version involves creating a release commit and tag, then aligning subsequent project milestones to ensure the release plan remains synchronized and traceable.

Does the release workflow require a clean git workspace and main branch checkout?

The release workflow requires a clean git workspace to prevent uncommitted changes from affecting the release. It enforces npm test on the main branch, warning but continuing on non-main branches.

How do I rebuild inline artifacts before creating a git release tag?

Rebuilding inline artifacts before creating a git release tag requires executing build scripts like build-inline.js and synchronizing generated outputs back into the working copy prior to the final release commit.

What happens if I run the version release workflow on a non-main branch?

Running the version release workflow on a non-main branch triggers a warning but continues execution. It still updates version references, rebuilds artifacts, and creates the release commit and tag.