release

Name: release
Availability: InStock
Author: krishsharma1008

Coordinate end-to-end Combyne releases across changelog, canaries, Docker tests, and GitHub.

Updated Aug 27, 2026

Search Tags:#automation #changelog #npm #github #release #docker #canary

Ready to run

npx skills add https://github.com/krishsharma1008/ADE --skill release-krishsharma1008

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/krishsharma1008/ADE/tree/main/skills/release
Command: npx skills add https://github.com/krishsharma1008/ADE --skill release-krishsharma1008

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Coordinate a full release across engineering verification, npm, GitHub, website publishing, and announcement follow-up. Use when leadership asks to ship a release, not merely to discuss version bumps.

Core Features & Use Cases

Stable changelog drafting via release-changelog
Canary publishing via scripts/release.sh --canary
Docker smoke testing via scripts/docker-onboard-smoke.sh
Stable publishing via scripts/release.sh
Pushing the release commit and tag
GitHub Release creation via scripts/create-github-release.sh
Website / announcement follow-up tasks

Quick Start

Initiate a full Combyne release workflow for the next version.

Frequently Asked Questions about release

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

FAQPage Schema

How do I coordinate a full npm and GitHub release with changelogs and Docker testing?▼

To coordinate a full npm and GitHub release, this Skill orchestrates changelog drafting, canary publishing, Docker smoke testing, and GitHub release creation. It manages the end-to-end pipeline from verification to publishing and announcements.

What is the best way to automate canary publishing for npm packages?▼

Automating canary publishing is handled by executing scripts/release.sh with the --canary flag. This allows you to publish pre-release versions to npm for testing before cutting a stable release.

How do I generate changelogs and release notes for major, minor, or patch releases?▼

Generating changelogs and release notes is orchestrated across major, minor, or patch releases using the release-changelog mechanism. It drafts stable changelogs and coordinates them into GitHub release notes.

Does this release workflow support Docker smoke testing before publishing?▼

Yes, Docker smoke testing is supported via scripts/docker-onboard-smoke.sh. It runs tests to verify your release before stable publishing and pushing the release commit.

Why does my release pipeline require a clean repository and last stable tag?▼

Your release pipeline requires a clean repository and last stable tag to enforce preconditions that prevent publishing errors. This ensures verification starts from a known stable state before coordinating release activities.

What downstream tasks are required after publishing a stable npm release?▼

After publishing a stable npm release, downstream tasks include pushing the release commit and tag, creating a GitHub release, and completing website or announcement follow-ups to finalize the release.