release

Coordinate CrewSpace release workflows from changelog drafting to GitHub release creation.

1|Updated Apr 12, 2026

Search Tags:#automation #changelog #github #release #ci #canary #smoke-testing

Ready to run

npx skills add https://github.com/priyansh19/CrewSpace --skill release-priyansh19

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Coordinating the full CrewSpace maintainer release workflow ensures safe, consistent, and timely software releases, from changelog drafting to final GitHub release.

Core Features & Use Cases

Can print and manage the stable changelog via release-changelog.
Validate canaries, promote canaries to stable, and publish releases ensuring CI gates and smoke tests pass.
Oversee post-release tasks such as website announcements and follow-up work.

Quick Start

Trigger a full CrewSpace release workflow for a chosen candidate and oversee changelog, tests, and GitHub release.

Frequently Asked Questions about release

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

FAQPage Schema

How do I coordinate an end-to-end GitHub release workflow with changelog drafting and smoke testing?▼

You can coordinate the full release workflow by triggering the lifecycle from changelog drafting to GitHub release creation. It enforces precondition checks for a clean repo, validates canaries, and runs smoke tests before promotion.

What is a canary validation process in a CI release pipeline?▼

Canary validation in a CI release pipeline tests a pre-release version before stable promotion. This workflow enforces CI gates and runs docker-onboard-smoke.sh tests to ensure the canary is safe before final release.

Do I need a clean repository before starting an automated release workflow?▼

Yes, a clean repository is required. The release workflow performs precondition checks to ensure the repo is clean and requires a target source_ref before drafting the changelog or creating a GitHub release.

Can I run a dry-run release to test changelog generation without publishing to npm?▼

Yes, you can run a dry-run release. The workflow supports dry-run options, allowing you to print and manage the stable changelog via release-changelog without executing the final GitHub release or npm publication.

What's the best way to manage post-release tasks like website announcements after a GitHub release?▼

The best way to manage post-release tasks is using a coordinated workflow that oversees follow-ups. After GitHub release creation and npm publication, it guides subsequent website announcements and remaining follow-up work.

Why does my automated release workflow fail precondition checks before creating a GitHub release?▼

Your release workflow fails precondition checks because the repository is not clean. The workflow enforces a clean repo state and requires valid inputs like a target source_ref before proceeding to changelog drafting or release creation.