release

Coordinate Paperclip releases across verification, publishing, and announcements.

Updated Apr 23, 2026

Search Tags:#changelog #npm #github #release #ci #canary #smoke-testing

Ready to run

npx skills add https://github.com/VitorRibeiro45/paperclip --skill release-vitorribeiro45

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate end-to-end Paperclip releases across engineering verification, npm publishing, GitHub Releases, and announcement follow-up to ensure consistent, auditable ship cycles.

Core Features & Use Cases

Canary validation and stable promotion coordination across CI, changelog drafting, and release publishing.
End-to-end workflow management including smoke testing, artifact promotion, and post-release communications.
Use Case: When leadership asks to ship a release, initiate the full workflow from candidate selection to public release notes and website updates.

Quick Start

Trigger the release workflow for the target canary or stable promotion after ensuring the latest changes are merged.

Frequently Asked Questions about release

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

FAQPage Schema

How do I coordinate end-to-end npm package releases across CI, GitHub, and website updates?▼

To coordinate end-to-end npm package releases, you need a workflow that manages canary validation, smoke testing, changelog drafting, GitHub Release creation, npm publishing, and post-release website announcements in an auditable sequence.

What is canary validation and how does it fit into a stable release promotion workflow?▼

Canary validation in a stable release promotion workflow involves running smoke tests and build validation on a canary artifact in CI before approving it for stable promotion to npm and GitHub Releases.

How do I automate changelog generation and GitHub Release creation for npm packages?▼

Automating changelog generation and GitHub Release creation requires a release workflow that drafts changelogs from merged changes, validates builds, and creates GitHub Releases as part of the npm publishing cycle.

Does this release workflow handle post-release communications and website announcements?▼

Yes, the release workflow handles post-release communications by generating follow-up website announcements and public release notes after the npm package is published and the GitHub Release is created.

What's the best way to manage canary checks and smoke testing before an npm publish?▼

The best way to manage canary checks and smoke testing before an npm publish is to trigger a coordinated release workflow that validates the canary build in CI and passes smoke tests before artifact promotion.

When do I need a coordinated release workflow for GitHub, npm, and website updates?▼

You need a coordinated release workflow for GitHub, npm, and website updates when leadership requests a ship cycle, requiring candidate selection, canary validation, changelog drafting, publishing, and public announcements to be fully auditable.