release

Coordinate software releases with changelog generation, canary verification, and npm publishing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates the manual overhead and human error associated with coordinating complex software releases, ensuring consistent verification, publishing, and announcement workflows.

Core Features & Use Cases

  • Automated Release Coordination: Manages the entire lifecycle from changelog drafting to GitHub release creation.
  • Verification Gates: Enforces strict smoke testing and build validation before stable promotion.
  • Use Case: When a product lead requests a stable release, this skill automatically verifies the candidate SHA, runs smoke tests, publishes the package, and updates the release documentation.

Quick Start

Use the release skill to promote the latest canary build to a stable release after verifying the candidate SHA.

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 from a verified commit?

You can automate npm publishing and GitHub release creation by coordinating the end-to-end software release lifecycle, which verifies the candidate SHA, runs smoke tests, publishes the package, and generates the git tag.

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

Promoting a canary build to a stable release requires enforcing strict smoke testing and build validation gates before stable promotion, ensuring the working tree is clean and the candidate SHA is verified.

Do I need a clean working tree to run deployment workflows?

Yes, executing deployment workflows requires a clean working tree, verified candidate SHAs, and appropriate npm and GitHub permissions to manage the release lifecycle successfully.

How does automated release coordination handle changelog generation?

Automated release coordination manages the entire lifecycle from drafting changelogs to creating GitHub releases, eliminating manual overhead and ensuring consistent verification and announcement workflows.

What are the limitations of automating software releases without verification gates?

Without verification gates, manual coordination risks human error, making strict smoke testing and build validation essential before stable promotion to ensure consistent publishing workflows.