release

Coordinate Paperclip canary and stable releases with CI-tested workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Paperclip release coordination eliminates manual handoffs and miscommunications by orchestrating changelog drafting, canary validation, and stable promotion across tooling and teams.

Core Features & Use Cases

  • End-to-end release orchestration: coordinates changelog, canary verification, stable promotion, smoke testing, and announcements.
  • Cross-team alignment: ensures upstream and downstream teams are in sync via gating and verification steps.
  • Post-release follow-up: handles website updates, GitHub Release creation, and release communications.

Quick Start

Initiate a release by selecting the candidate, drafting the stable changelog, validating the candidate, performing smoke testing, and publishing the GitHub Release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate software release coordination from changelog drafting to GitHub Release creation?

Automate software release coordination by orchestrating changelog drafting, canary validation, stable promotion, Docker smoke tests, and GitHub Release creation through CI-tested workflows. It requires inputs like target source_ref, release type, dry-run flag, and release context to eliminate manual handoffs.

How does canary validation work during a stable release promotion?

Canary validation works during stable release promotion by enforcing verification gates and Docker smoke tests before escalating changes. The workflow aligns upstream and downstream teams, ensuring the candidate passes CI-tested canary paths before stable promotion occurs.

What inputs do I need to start an end-to-end release workflow?

To start an end-to-end release workflow, you need to provide a target source_ref, release type (canary or stable), dry-run flag, and release context. These inputs trigger the orchestration of changelog drafting, smoke testing, and GitHub Release creation.

Can I use dry-run mode for canary releases to test the coordination process?

Yes, you can use a dry-run flag for canary releases to test the coordination process. The workflow enforces prerequisites and verification gates, allowing you to validate the release context and CI-tested paths before executing actual stable promotion or GitHub Release creation.

Does this release coordinator handle post-release tasks like website updates and announcements?

Yes, the release coordinator handles post-release tasks by automating website updates, GitHub Release creation, and release communications. This ensures cross-team alignment and completes the end-to-end release orchestration after stable promotion and smoke testing finish.

What is the best way to coordinate changelog drafting and cross-team alignment for CI releases?

The best way to coordinate changelog drafting and cross-team alignment is using an end-to-end release orchestration workflow. It enforces verification gates and prerequisites, ensuring upstream and downstream teams stay synchronized via CI-tested canary and stable promotion paths.