release

Coordinate end-to-end Paperclip release workflows including canary validation, builds, tests, and npm publishing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate and automate end-to-end release workflows for Paperclip, ensuring changelog accuracy, canary validation, builds, tests, and public deployment.

Core Features & Use Cases

  • Stable changelog drafting via release-changelog
  • Canary verification and publish status from master
  • Docker-based smoke testing and validation
  • Manual stable promotion from a chosen source ref
  • GitHub Release creation and publication
  • Website/announcement follow-up tasks

Quick Start

Trigger a release by stating the goal in natural language, for example 'do a release' to start the end-to-end workflow.

Frequently Asked Questions about release

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

FAQPage Schema
How do I coordinate an npm package release with canary validation and GitHub releases?

To coordinate an npm package release, the workflow validates candidate SHAs, runs canary validation from master, executes type checks and builds, performs smoke testing, and publishes artifacts and GitHub release notes.

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

Promoting a canary build to a stable release requires manual stable promotion from a chosen source ref, enforcing specific inputs, validating the candidate SHA, and running type checks and builds before publication.

How do I automate changelog generation and website announcements for a software release?

Automating changelog generation and website announcements involves drafting a stable changelog, creating a GitHub release, and executing website and announcement follow-up tasks across master and release pipelines.

Does the release workflow support Docker-based smoke testing before publishing?

Yes, Docker-based smoke testing and validation are supported as core features, running alongside type checks and builds to verify artifacts before stable promotion and npm publication.

What are the limitations of automating end-to-end release cycles across master and release pipelines?

Limitations include the requirement to enforce specific inputs and validate candidate SHAs manually, meaning the workflow depends on correct source refs and successful canary verification before stable promotion.