release

Automate Sprint releases from canary to stable with changelog, testing, and GitHub Release.

Updated Mar 25, 2026

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

Ready to run

npx skills add https://github.com/gancim/sprint --skill release-gancim

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Coordinate a full Sprint maintainer release workflow, not just an npm publish.

Core Features & Use Cases

Orchestrates canary validation, manual promotion, and stable release steps
Automates changelog drafting, GitHub release creation, and post-release activities
Supports smoke testing and stakeholder announcements

Quick Start

Initiate a full release from master and publish a GitHub release after successful canary validation.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate Sprint release workflows from canary to stable?▼

Automate Sprint release workflows by orchestrating canary validation, manual promotion, and stable release steps across changelog drafting, smoke testing, and GitHub release creation.

What is the best way to coordinate changelog drafting and GitHub release creation together?▼

Coordinate changelog drafting and GitHub release creation by automating end-to-end Sprint maintainer release tasks, ensuring post-release activities and stakeholder announcements are included.

How do I validate canary releases before promoting to stable?▼

Validate canary releases by running smoke testing and canary verification status checks before manually promoting a chosen source ref to the stable channel.

Can I use GitHub releases for full Sprint maintainer workflows beyond just npm publish?▼

Use GitHub releases for full Sprint maintainer workflows by coordinating canary validation, promotion decisions, changelog updates, and post-release communications beyond simple npm publishing.

What steps are needed to publish a GitHub release after successful canary validation from master?▼

Initiate a full release from master, execute canary validation, run smoke tests, manually promote the source ref, and publish the GitHub release after successful verification.

When should I use an end-to-end Sprint release workflow instead of manual releases?▼

Use an end-to-end Sprint release workflow when you need coordinated canary-to-stable promotion, automated changelog drafting, smoke testing, and post-release stakeholder communications.