release

Coordinate end-to-end Paperclip canary and stable releases with verification gates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manual, ad-hoc Paperclip release processes often skip critical steps like changelog drafting, smoke testing, and post-release follow-up, leading to incomplete or broken releases that impact users.

Core Features & Use Cases

  • End-to-End Release Coordination: Manages the full lifecycle of both canary and stable Paperclip releases, from candidate selection to post-release follow-up.
  • Automated Verification & Testing: Enforces pre-release verification gates and Docker smoke testing to catch issues before stable promotion.
  • Use Case: When leadership requests a stable Paperclip release, this skill ensures all preconditions are met, the changelog is drafted, smoke tests pass, and announcement follow-up tasks are created, eliminating missed release steps.

Quick Start

Use the release skill to coordinate the next stable Paperclip release after the latest canary passes all verification checks.

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 npm publishing workflow for canary and stable releases?

End-to-end npm publishing coordination manages the full release lifecycle from candidate selection to post-release follow-up, enforcing pre-release verification gates and Docker smoke testing before stable promotion.

What is the best way to automate changelog drafting and GitHub Release creation for software deployment?

Automated changelog drafting and GitHub Release creation are enforced as critical steps within a full release coordination process, ensuring no documentation or publishing steps are skipped during software deployment.

How does Docker smoke testing work during pre-release verification for stable promotion?

Docker smoke testing acts as a pre-release verification gate to catch issues before stable promotion, ensuring canary validation passes before proceeding to npm publishing and GitHub Release creation.

Why does my manual release process skip critical steps like post-release announcements and rollback handling?

Manual ad-hoc release processes often skip post-release announcements and rollback handling because they lack enforced end-to-end coordination, leading to incomplete or broken stable publishes.

How do I handle rollback when a stable npm publish fails during software deployment?

Rollback handling for failed stable publishes is managed by enforcing a commit-driven release model with pre-release verification gates, ensuring failed deployments are addressed without missing critical recovery steps.

Do I need a commit-driven release model to use automated release coordination for canary validation?

A commit-driven release model is required for automated release coordination, ensuring canary validation, stable promotion, and npm publishing adhere to pre-release verification gates and post-release announcement tasks.