release

Coordinate software releases with pre-flight checks, changelog generation, canary publishing, and smoke testing.

Updated Mar 13, 2026

Search Tags:#automation #changelog #versioning #deployment #npm #release

Ready to run

npx skills add https://github.com/tbuijibing/jigongopc --skill release-tbuijibing

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex, multi-step process of releasing new software versions, ensuring consistency and reducing manual errors across engineering, website updates, and public announcements.

Core Features & Use Cases

End-to-End Release Coordination: Manages changelog generation, canary publishing, smoke testing, promotion to latest, and follow-up task creation for website and marketing announcements.
Idempotent & Resumable: Designed to be safely re-run, allowing users to pick up where they left off if a step fails or needs refinement.
Use Case: When the CTO requests "release v1.2.0", this Skill orchestrates the entire process from code tagging to social media announcements, ensuring a smooth and professional rollout.

Quick Start

Use the release skill to perform a patch release for the project.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate changelog generation and version bumping for npm deployments?▼

Automate changelog generation and version bumping by analyzing git commits to determine the correct version increment, then automatically drafting the release notes for the npm deployment.

What is the best way to coordinate end-to-end software releases with canary publishing and smoke testing?▼

Coordinating end-to-end software releases involves sequencing pre-flight checks, canary publishing, and smoke testing to validate stability before promoting the build to the latest tag.

Can I resume a failed software deployment and pick up where I left off?▼

You can resume a failed software deployment because the release process is idempotent, allowing you to safely re-run the workflow and pick up exactly where the previous execution failed.

How do I create cross-project follow-up tasks for website publishing and social media announcements after a release?▼

Create cross-project follow-up tasks for website publishing and social media announcements by automatically generating linked tickets upon successful promotion of the release artifacts.

Does automated release coordination handle pre-flight checks before promoting to the latest tag?▼

Automated release coordination performs pre-flight checks before promotion to the latest tag, ensuring all validation gates pass and release artifacts are properly linked upon completion.