release

Coordinate software releases with changelog generation, version management, and npm publishing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the complex, multi-step process of coordinating a full software release, ensuring all necessary engineering, publishing, and announcement tasks are completed systematically.

Core Features & Use Cases

  • End-to-End Release Management: Manages changelog drafting, version bumping, canary and stable publishing, smoke testing, and GitHub release creation.
  • Maintainer Workflow: Designed for scenarios where leadership requests a release, moving beyond simple version bumps to a comprehensive deployment process.
  • Use Case: When a product lead says "ship the next patch release," this skill will draft the changelog, publish a canary version, smoke test it, publish the stable version, and create the GitHub release notes.

Quick Start

Use the release skill to perform a patch release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate npm publishing and GitHub release creation for a patch version?

Automate npm publishing and GitHub release creation by coordinating the complete software release process, which handles version bumping, publishing, and GitHub release notes generation in a single workflow.

What is the best way to orchestrate a full software release with canary versions?

Orchestrate a full software release by publishing a canary version, running smoke tests, and then publishing the stable version, ensuring engineering verification before final deployment.

How does changelog generation work during version management?

Changelog generation works by automatically drafting release notes as part of the version management process, ensuring all deployment tasks and changes are systematically recorded before publishing.

Can I use GitHub Actions to handle both stable and canary deployments?

Yes, you can handle both stable and canary deployments by enforcing an adherence to a defined release model, ensuring distinct workflows for canary testing and stable production releases.

What steps are required to move beyond a simple version bump to a full deployment process?

Moving beyond a simple version bump requires drafting the changelog, publishing a canary version, smoke testing, publishing the stable version, and creating the GitHub release notes.

When do I need a comprehensive release process instead of a manual version bump?

You need a comprehensive release process when leadership requests a full deployment, requiring engineering verification, npm publishing, GitHub release creation, and post-release communication.