release

Name: release
Availability: InStock
Author: avishai-tsabari

Coordinate Paperclip release operations across changelog, verification, publishing, and announcements.

Updated Mar 19, 2026

Search Tags:#automation #changelog #release #canary #github-release #stable

Ready to run

npx skills add https://github.com/Avishai-Tsabari/agents_manager --skill release-avishai-tsabari

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Avishai-Tsabari/agents_manager/tree/main/.agents/skills/release
Command: npx skills add https://github.com/Avishai-Tsabari/agents_manager --skill release-avishai-tsabari

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Coordinate end-to-end release operations for Paperclip across changelog, verification, publishing, and announcements to ensure a smooth, auditable rollout.

Core Features & Use Cases

Stable changelog drafting via release-changelog
Canary verification and publish status from master
Docker smoke testing via scripts/docker-onboard-smoke.sh
Manual stable promotion from a chosen source ref
GitHub Release creation
Website / announcement follow-up tasks

Quick Start

Trigger the release workflow with a candidate, then monitor changelog creation, canary and stable validation, smoke testing, and GitHub release status.

Frequently Asked Questions about release

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

FAQPage Schema

How do I coordinate end-to-end software releases including changelog generation and GitHub Release creation?▼

To coordinate a stable release, you trigger the workflow with a validated source ref and release date, then monitor automated changelog drafting, Docker smoke testing, canary verification, and GitHub Release creation for an auditable rollout.

What is the canary validation process for a new release candidate?▼

Canary validation verifies the publish status from master before a full rollout. It ensures the release candidate passes automated checks and Docker smoke testing, confirming stability before you proceed to manual stable promotion.

How do I generate a stable changelog before publishing a GitHub Release?▼

Stable changelog generation uses the release-changelog mechanism to draft release notes automatically. It processes validated inputs like the candidate source ref and release date to produce an auditable changelog prior to GitHub Release creation.

Does this release workflow support dry-run flag execution and Docker smoke testing?▼

Yes, the release workflow validates a dry-run flag for safe execution and uses scripts/docker-onboard-smoke.sh for Docker smoke testing. These features verify the candidate source ref before stable promotion.

What are the limitations when promoting a stable release from a chosen source ref?▼

Stable promotion requires careful validation of the source ref, dry-run flag, and release date inputs. Limitations include dependencies on successful canary verification, automated checks, and Docker smoke testing before manual promotion can proceed.

Can I automate post-release website announcements and follow-up tasks?▼

Yes, post-release follow-up tasks include website updates and announcement coordination. After stable promotion and GitHub Release creation, the workflow automates these downstream actions to complete the end-to-end release cycle.