release

Coordinate end-to-end Paperclip release workflows across npm publish and GitHub releases.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Kauedz/althius-alg --skill release-kauedz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Kauedz/althius-alg/tree/main/.agents/skills/release
Command: npx skills add https://github.com/Kauedz/althius-alg --skill release-kauedz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Coordinate a full Paperclip release workflow across engineering verification, npm publishing, GitHub releases, and announcements, reducing manual coordination errors and delays.

Core Features & Use Cases

  • Automated preflight checks and validations to ensure a clean, auditable release process.
  • End-to-end coordination from canary to stable, including changelog drafting, canary verification, smoke testing, and release announcements.
  • Manual promotion capabilities with clear rollback and status reporting to stakeholders.

Quick Start

Initiate a release by selecting a candidate source ref and choosing canary or stable mode, then run the release workflow.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate an end-to-end npm publish and GitHub release workflow?

Automate an npm publish and GitHub release workflow by coordinating preflight checks, changelog drafting, tag creation, and post-release announcements. The workflow supports both canary and stable release scenarios to reduce manual coordination errors.

Can I run a canary release with smoke testing before a stable npm publish?

Yes, you can run a canary release with smoke testing before a stable npm publish. The workflow applies verification gates and collects inputs to validate canary versions before promoting them to a stable release.

What is the best way to draft changelogs and create git tags for CI-CD releases?

Draft changelogs and create git tags for CI-CD releases by executing the multi-step release workflow. It enforces preconditions, handles tag creation automatically, and reports final status including version numbers and release artifacts.

Does the release workflow support dry-run mode for GitHub releases?

Yes, the release workflow supports dry-run mode for GitHub releases. You can validate the end-to-end coordination process, including preflight checks and changelog drafting, without executing live npm publish or tag creation.

How do I handle rollback and status reporting during a manual release promotion?

Handle rollback and status reporting during manual release promotion by using the workflow's built-in verification gates. It reports final status including git tags, version numbers, and release artifacts to keep stakeholders informed.

When should I not use an automated workflow for npm publishing?

You should not use an automated workflow for npm publishing when preconditions are unmet or verification gates fail. The workflow enforces these checks to prevent releasing unverified code, ensuring a clean, auditable process.