neb-release

Coordinate platform releases across npm, GitHub, smoke tests, and announcements.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neb-release
Source: https://github.com/nebinfra/nebcore-ai-skills/tree/main/neb-release
Command: npx skills add https://github.com/nebinfra/nebcore-ai-skills --skill neb-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Coordinate a full platform release across engineering verification, npm, GitHub, smoke testing, and announcement follow-up. Use when leadership asks to ship a release, not merely to discuss versioning.

Core Features & Use Cases

  • Changelog drafting via release-changelog
  • Canary verification and publish status from master
  • Docker smoke testing via scripts/docker-onboard-smoke.sh
  • Manual stable promotion from a chosen source ref
  • GitHub Release creation
  • Website / announcement follow-up tasks

Quick Start

Trigger the full platform release workflow to coordinate changelog, verification, testing, promotion, and release publication

Frequently Asked Questions about neb-release

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

FAQPage Schema
How do I coordinate a full platform release across multiple phases?

A full platform release coordinates multi-phase steps including changelog drafting, canary verification, Docker smoke testing, manual stable promotion, GitHub Release creation, and post-release announcement tasks across teams and repos.

What is the process for canary verification before a stable release?

Canary verification checks the publish status from master to validate the release candidate. After canary verification succeeds, you can proceed with manual stable promotion from a chosen source ref to finalize the deployment.

How do I automate changelog drafting for a GitHub release?

Changelog drafting is automated via release-changelog to collect commit history before publication. This drafted changelog is then used during the GitHub Release creation step to document the shipped changes.

Does this release workflow handle Docker smoke testing?

Yes, Docker smoke testing is executed via scripts/docker-onboard-smoke.sh during the release workflow. This verifies the deployment integrity before you proceed to manual stable promotion and final announcement follow-up tasks.

When should I use an end-to-end release workflow instead of just publishing a version?

You should use an end-to-end release workflow when leadership asks to ship a release, not merely discuss versioning. It ensures comprehensive verification, testing, and coordinated post-release follow-ups across engineering teams.

Can I manually promote a stable release from a specific source ref?

Yes, manual stable promotion can be executed from a chosen source ref after canary verification and Docker smoke testing pass. This ensures the stable release is published from a verified and tested codebase state.