release

Coordinate end-to-end Paperclip releases across verification, publishing, and announcements.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate end-to-end Paperclip releases across verification, publishing, and announcements, reducing manual handoffs and risk.

Core Features & Use Cases

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

Quick Start

Trigger the release workflow (canary or stable) from your repository and follow prompts to complete verification, publishing, and 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 release from canary to stable?

Coordinate end-to-end releases by enforcing a clean working tree, running canary validation and Docker smoke tests, then generating changelogs and creating GitHub releases for safe, auditable promotions from canary to stable.

What's the best way to automate changelog generation for GitHub releases?

Automate changelog generation for GitHub releases by triggering the stable release workflow, which drafts changelogs via release-changelog and integrates them directly into the GitHub Release creation process.

Do I need a clean working tree to publish a canary release?

Yes, a clean working tree is a required prerequisite to publish a canary release, ensuring safe, auditable promotion from canary to stable without uncommitted changes interfering with validation.

Can I manually promote a stable release from a specific source ref?

Yes, manual stable promotion from a chosen source ref is supported, allowing you to validate canary publish status from master and trigger a controlled, auditable release workflow.

Does this release workflow include Docker smoke testing?

Yes, Docker smoke testing is integrated via an onboard script within the release workflow, verifying container integrity before proceeding to publishing and GitHub release creation.

What follow-up tasks are needed after creating a GitHub release?

Post-release follow-up tasks include website updates and announcement coordination, completing the end-to-end release workflow across verification, publishing, and announcements.