release

Coordinate Paperclip release workflows from master to GitHub Release.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates coordinating a complete Paperclip release workflow from master to GitHub Release, including changelog preparation, canary verification, and Docker-based smoke testing, so teams can ship confidently.

Core Features & Use Cases

  • End-to-end release orchestration: changelog drafting, canary verification, and stable promotion.
  • Automated testing and publishing: Docker smoke tests and GitHub Release creation.
  • Follow-up tasks: website announcements and release communications after publish.

Quick Start

Trigger the release workflow for a chosen candidate and run it in live mode to publish.

Frequently Asked Questions about release

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

FAQPage Schema
How do I coordinate a full release workflow from master to a GitHub Release?

Coordinating a full release workflow involves automating changelog drafting, canary verification, and GitHub Release creation from the master branch. This skill orchestrates that entire pipeline end-to-end.

Can I run a dry-run release before publishing to GitHub?

Yes, you can run a dry-run release. The skill enforces release context inputs, allowing you to validate the workflow and perform Docker smoke testing without actually publishing to GitHub.

How does Docker smoke testing work during a canary release verification?

Docker smoke testing during canary release verification executes the docker-onboard-smoke.sh script to validate deployment stability. It ensures the release candidate works correctly before stable promotion.

What is the best way to promote a canary build to stable?

The best way to promote a canary build to stable is to apply this release skill. It validates the candidate source_ref, runs canary verification, and executes stable promotion upon successful smoke testing.

Do I need to manually draft a changelog before triggering the release workflow?

No, manual changelog drafting is not required. The skill leverages release-changelog integration to automatically prepare the changelog as part of the orchestrated release workflow.

What follow-up tasks are handled after publishing a GitHub Release?

After publishing a GitHub Release, the skill handles follow-up tasks such as website announcements and release communications. This ensures stakeholders are informed post-publish.