release

Coordinate Paperclip release workflows across verification, publishing, and announcements.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/elijahbowie/ArchonOS --skill release-elijahbowie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/elijahbowie/ArchonOS/tree/main/.agents/skills/release
Command: npx skills add https://github.com/elijahbowie/ArchonOS --skill release-elijahbowie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates a full Paperclip release workflow across engineering verification, npm publishing, GitHub releases, 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: coordinates stable changelog notes via the release-changelog tool.
  • Canaries and verification: tracks canary status from master and ensures verification gates pass.
  • Smoke testing: triggers Docker-based onboarding smoke tests to validate end-to-end stability.
  • Promotion and publishing: manages manual stable promotions, GitHub Release creation, and artifact publishing.
  • Communication: coordinates website updates and post-release announcements.

Quick Start

Initiate a full release workflow and monitor changelog generation, canary checks, and post-release announcements.

Frequently Asked Questions about release

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

FAQPage Schema
How do I coordinate an end-to-end npm package release with changelog and smoke testing?▼

Coordinating an end-to-end npm release requires drafting changelogs, validating canary builds, running Docker smoke tests, and publishing artifacts. This workflow enforces verification gates and validates candidate SHAs before promoting a stable release.

What is a canary release validation workflow for GitHub projects?▼

A canary release validation workflow tracks canary status from master to ensure verification gates pass before stable promotion. It triggers Docker-based smoke tests to validate end-to-end stability prior to creating a GitHub Release.

Do I need npm publish rights to create a GitHub Release for my project?▼

Yes, npm publish rights are required for this release workflow. The process enforces prerequisites, validates candidate SHAs, and guarantees you have the necessary permissions to publish artifacts correctly before creating a GitHub Release.

How do I automate changelog drafting for stable software releases?▼

Automating changelog drafting for stable releases involves coordinating notes via a release-changelog tool. This step integrates into a broader workflow encompassing canary validation, Docker smoke testing, and manual stable promotion.

What steps are needed for post-release announcements and website updates?▼

Post-release announcement steps involve coordinating website updates and communication follow-ups after artifact publishing. This guarantees the release is communicated correctly once the GitHub Release and npm publishing are complete.

When should I use Docker smoke testing in a release management workflow?▼

Docker smoke testing is used in a release management workflow to validate end-to-end stability before manual stable promotion. It ensures the release candidate functions correctly after canary validation and prior to GitHub Release creation.