release

Coordinate Staple release workflows across verification, packaging, and announcements.

2|Updated Mar 29, 2026

Search Tags:#automation #workflow #changelog #github #release #canary

Ready to run

npx skills add https://github.com/rishith-c/staple --skill release-rishith-c

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/rishith-c/staple/tree/main/.agents/skills/release
Command: npx skills add https://github.com/rishith-c/staple --skill release-rishith-c

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate end-to-end Staple release workflows across verification, packaging, and release announcements.

Core Features & Use Cases

Stable changelog drafting via release-changelog and manual edits for canaries
Canary verification and publish status tracking from master
Docker smoke testing using scripts/docker-onboard-smoke.sh
Manual stable promotion from a chosen source ref
GitHub Release creation and website / announcement follow-up tasks

Quick Start

Run the release workflow by specifying the candidate source_ref and the desired stable date.

Frequently Asked Questions about release

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

FAQPage Schema

How do I orchestrate end-to-end release workflows from verification to GitHub announcements?▼

End-to-end release workflows are orchestrated by coordinating verification, packaging, and announcements. This requires a clean working tree, a candidate SHA, release tooling access, and npm or GitHub publishing rights to ship the release.

What is the process for promoting a canary release to stable?▼

Promoting a canary to stable involves manual stable promotion from a chosen source ref. The workflow tracks canary verification and publish status from master before drafting the stable changelog.

Do I need a clean working tree and a candidate SHA to cut a stable release?▼

Yes, cutting a stable release requires a clean working tree and a candidate SHA. You also need access to release tooling like release-changelog and release.sh, plus npm or GitHub publishing rights.

How to run Docker smoke tests before publishing a canary?▼

Docker smoke testing is run using scripts/docker-onboard-smoke.sh. This verifies the canary build integrity before tracking the publish status from master and proceeding with the release workflow.

Can I draft a stable changelog automatically and then apply manual edits for canaries?▼

Yes, stable changelog drafting is handled via release-changelog, while manual edits are applied specifically for canaries. This ensures accurate release notes before creating the GitHub Release and website announcements.