release

Coordinates Paperclip release process including verification, changelog creation, Docker smoke testing, and GitHub Release publishing.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/mighty-hq/mighty-paperclip --skill release-mighty-hq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/mighty-hq/mighty-paperclip/tree/main/.agents/skills/release
Command: npx skills add https://github.com/mighty-hq/mighty-paperclip --skill release-mighty-hq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk and coordination overhead of shipping a Paperclip release by guiding a complete, verification-first maintainer workflow instead of only handling versioning or npm publishing.

Core Features & Use Cases

  • Stable changelog drafting: Generates or updates the stable-only release notes at releases/vYYYY.MDD.P.md using release-changelog, preserving manual edits and avoiding canary changelog creation.
  • Canary verification and publish status checks: Validates that the latest canary path on master completed successfully (verification passed, npm canary published, and the expected canary tag exists).
  • Docker smoke testing: Executes the Docker onboarding smoke test for the canary using scripts/docker-onboard-smoke.sh to confirm install, server boot, UI load, and basic onboarding.
  • Stable promotion and GitHub Release creation: Runs the stable publish workflow (dry-run first when practical), ensures tagging and the GitHub Release are created/updated from the stable notes, and then performs website/announcement follow-up tasks.

Use Case Example: When leadership instructs you to “promote this canary to stable,” this Skill drafts the stable changelog, gates verification, runs smoke testing, promotes the verified commit to the correct YYYY.MDD.P version, creates the GitHub Release, and prepares the website and announcement updates.

Quick Start

Use the release Skill to coordinate a stable promotion by setting the target source_ref, stable_date, and dry_run status.

Frequently Asked Questions about release

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

FAQPage Schema
How do I promote a verified canary build to a stable npm release?

Promoting a canary to stable requires gating the candidate SHA, running docker smoke testing, executing the stable publish workflow, and creating the corresponding GitHub Release with website follow-ups.

What is the process for generating a stable changelog without overwriting manual edits?

Changelog generation uses release-changelog to update stable notes at releases/vYYYY.MDD.P.md, preserving manual edits and avoiding canary changelog creation.

How do I run docker smoke testing before publishing a release?

Docker smoke testing runs scripts/docker-onboard-smoke.sh against the canary to confirm install, server boot, UI load, and onboarding before triggering the stable workflow.

What preconditions must pass before coordinating a full release?

Precondition checks require a clean working tree, candidate SHA gating, pnpm lock refresh on master when needed, and successful canary verification with npm publish and expected tag existence.

Does the release workflow support dry-run executions for stable promotion?

The stable publish workflow runs a dry-run first when practical to validate the promotion path before executing the actual stable version publish and GitHub Release creation.

How does canary verification validate npm publish status before stable promotion?

Canary verification validates that the latest master path completed successfully by checking verification status, npm canary package publication, and expected canary tag existence before stable promotion.