release

Coordinate Paperclip releases from canary validation to GitHub release.

Updated Aug 27, 2026

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

Ready to run

npx skills add https://github.com/Mothership-Foundry/foundry-dashboard --skill release-mothership-foundry

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Mothership-Foundry/foundry-dashboard/tree/main/.agents/skills/release
Command: npx skills add https://github.com/Mothership-Foundry/foundry-dashboard --skill release-mothership-foundry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Coordinate a full Paperclip release workflow 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 coordination: Draft and publish stable changelogs via releases/vYYYY.MDD.P.md.
Verification & publishing: Manage canary and stable promotions, smoke tests, and npm publish gates.
End-to-end release orchestration: Coordinate GitHub Release creation and website/announcement follow-up tasks.

Quick Start

Trigger the release workflow for a chosen source ref and monitor preconditions through to the final GitHub release and announcement tasks.

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 workflow from canary to stable?▼

To coordinate a full npm and GitHub release workflow, you trigger the release process from a chosen source ref to manage canary promotions, enforce verification gates, execute npm publishing, and create the final GitHub release. It handles end-to-end orchestration across multiple systems.

What is the best way to automate changelog drafting and version calculation for npm publishing?▼

Automating changelog drafting and version calculation involves enforcing preconditions, computing target versions, and generating release artifacts like releases/vYYYY.MDD.P.md. This process ensures stable changelog coordination before executing npm publish gates and GitHub release creation.

How does a canary smoke test validation gate work before a stable release?▼

A canary smoke test validation gate works by enforcing preconditions during canary promotions before allowing a stable release. It runs verification checks to ensure the canary version passes specific tests, preventing faulty code from advancing to the final npm and GitHub publishing stages.

Can I manage Docker and website announcement follow-ups as part of an end-to-end release orchestration?▼

You can manage Docker and website announcement follow-ups as part of end-to-end release orchestration. The workflow orchestrates multi-system publishing across GitHub, npm, Docker, and the website, coordinating announcement follow-up tasks after the core release artifacts are generated and published.

Do I need specific source refs or dependencies to trigger a canary promotion to a stable release?▼

You need a chosen source ref to trigger the release workflow, but no specific external dependencies are required. The system enforces its own preconditions and computes target versions internally to validate the canary promotion before proceeding to stable npm publishing and GitHub release creation.