release

Name: release
Availability: InStock
Author: ulle73

Orchestrate Paperclip software release workflows from changelog drafting to GitHub Release creation.

Updated Apr 13, 2026

Search Tags:#release management #version control #CI/CD #software release #github release #paperclip

Ready to run

npx skills add https://github.com/ulle73/paperclip --skill release-ulle73

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/ulle73/paperclip/tree/main/.agents/skills/release
Command: npx skills add https://github.com/ulle73/paperclip --skill release-ulle73

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manages the complex process of preparing and releasing updates to Paperclip, ensuring every step is executed smoothly and correctly.

Core Features & Use Cases

End-to-End Workflow: Automates release preparation, verification, and publishing across engineering, npm, GitHub, and testing.
Version Control: Ensures the correct versioning of releases by managing canary and stable tags.
Canary and Stable Release Management: Handles the promotion of canary versions to stable with thorough smoke testing.
Follow-up Tasks: Tracks follow-up work like updating documentation and making announcements post-release.
Use Case: When a stable release needs to be cut from a feature branch or a pull request has been merged that requires a release, this skill streamlines the process.

Quick Start

Execute the 'release' skill when preparing a new version of Paperclip to be promoted to stable.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate a GitHub release for Paperclip from a merged pull request?▼

To automate a GitHub release for Paperclip, you orchestrate the software release workflow from changelog drafting to GitHub Release creation and follow-up tasks using pre-defined commit-driven release models after a pull request merges.

What is the process for promoting a canary release to a stable version?▼

Promoting a canary release to a stable version involves version control management and thorough smoke testing. The workflow handles canary and stable tags to ensure correct versioning before final promotion.

Do I need npm and GitHub access to manage software releases with this workflow?▼

Yes, you need npm for publishing, GitHub for Releases, and local scripts for additional tasks. The workflow requires access to these environments to orchestrate the end-to-end release process completely.

What follow-up tasks are required after publishing a stable Paperclip release?▼

After publishing a stable Paperclip release, follow-up tasks include updating documentation and making announcements. The workflow tracks these post-release activities to ensure they are executed.

Can I cut a stable release directly from a feature branch?▼

Yes, you can cut a stable release directly from a feature branch. The workflow streamlines the process when a stable release needs to be cut from a feature branch or after a pull request merges.