skills.rest
travelinman1013
travelinman1013COMMUNITY
Explore all skills by this author →
GitHub

release

Coordinate Paperclip releases across npm, GitHub, Docker smoke tests, and changelog drafting.

Updated Apr 16, 2026
Search Tags:#workflow#changelog#github#release#docker#canary#stable
One-click install
npx skills add https://github.com/travelinman1013/royclip --skill release-travelinman1013
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/travelinman1013/royclip/tree/main/.agents/skills/release
Command: npx skills add https://github.com/travelinman1013/royclip --skill release-travelinman1013

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Coordinate a full Paperclip release across engineering verification, npm, GitHub, smoke testing, and announcement follow-up. Use when leadership asks to ship a release, not merely to discuss versioning.

Core Features & Use Cases

  • Release 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 a full release workflow for a chosen candidate ref using the stable release path and follow the steps outlined in this skill.

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 end-to-end software release across npm, GitHub, and Docker?▼

A full end-to-end software release requires coordinating engineering verification, npm, GitHub, Docker smoke testing, and announcement follow-up. The workflow covers changelog drafting, canary verification, manual promotions, and GitHub Releases for a validated candidate SHA.

What's the best way to promote a canary release to stable?▼

Promoting a canary release to stable requires canary verification from master, running Docker smoke tests via scripts, and manual stable promotion from a chosen source ref. This validates the candidate SHA before final GitHub Release creation.

Do I need a clean repo state before starting a release workflow?▼

Yes, a clean repo state is required before starting a release workflow. You also need a validated candidate SHA and access to scripted release tools such as release-changelog and docker-onboard-smoke.sh to execute the end-to-end promotion safely.

How do I draft a changelog for a GitHub Release?▼

Drafting a changelog for a GitHub Release uses a release-changelog script within the release workflow. This prepares the necessary documentation for GitHub Release creation and subsequent website announcement follow-up tasks.

Why does my Docker smoke test fail during the release process?▼

Docker smoke tests via scripts/docker-onboard-smoke.sh fail if the repo state is unclean or the candidate SHA is unvalidated. Meeting prerequisites like a clean repo and validated candidate SHA before triggering the release workflow prevents these failures.

Related Skills

Explore More Software Engineering Skills→
rishith-crishith-c
2

release

Coordinate Staple release workflows across verification, packaging, and announcements.

Community
Advanced
VitorRibeiro45VitorRibeiro45

release

Coordinate Paperclip releases across verification, publishing, and announcements.

Community
Advanced
yu-iskwyu-iskw

dbt-tools-web-pack-npx-smoke

Packs the @dbt-tools/web package and smoke-tests its CLI via npx.

Community
Advanced
richardadonnellrichardadonnell
45

semantic-versioning

Automate semantic versioning and changelog generation from conventional commits.

Community
Advanced