release

Automate release management with SemVer tagging, artifact signing, changelog generation, and smoke testing.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/nist0/CoDev --skill release-nist0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/nist0/CoDev/tree/main/.github/skills/release
Command: npx skills add https://github.com/nist0/CoDev --skill release-nist0

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the end-to-end release process, from SemVer tagging to artifact signing, changelog generation, smoke testing, and rollback capabilities.

Core Features & Use Cases

  • End-to-End Pipeline: Manages SemVer tagging, artifact signing, changelog automation, smoke testing, and rollback for a secure release process.
  • Version Control: Automates version tagging based on Conventional Commits.
  • Artifact Management: Handles artifact signing, SBOM generation, and signature publishing.
  • Deployment: Supports publishing to GitHub Releases, container registries, and package repositories like NuGet, PyPI, npm.
  • Post-Deployment Verification: Performs smoke tests and monitors for post-deployment issues.
  • Rollback: Provides a documented rollback procedure for quick recovery in case of issues.

Quick Start

Execute the release command with the version and target environment, e.g., 'release 1.2.3 production'.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate end-to-end release management with SemVer tagging and artifact signing?

End-to-end release management is automated by handling SemVer tagging, artifact signing, changelog generation, smoke testing, and rollback procedures within a single pipeline. You can execute a release command with the target version and environment.

How does SemVer tagging work with Conventional Commits in a CI/CD pipeline?

SemVer tagging automates version bumping by parsing Conventional Commits history. The pipeline analyzes commit messages to determine whether to increment major, minor, or patch versions before applying the tag during deployment.

Can I use this release pipeline automation for publishing to container registries and package repositories?

Yes, pipeline automation supports publishing artifacts to GitHub Releases, container registries, and package repositories like NuGet, PyPI, and npm, handling signing and SBOM generation during the deployment process.

What is the best way to handle rollback and post-deployment verification in a release pipeline?

Rollback and post-deployment verification are handled by performing automated smoke tests and monitoring for issues immediately after deployment. If problems arise, a documented rollback procedure enables quick recovery.

Does artifact signing include SBOM generation and signature publishing for software deployment?

Yes, artifact signing includes SBOM generation and signature publishing. The pipeline manages these security artifacts alongside the deployment process to ensure a secure and verifiable release.

When do I need automated changelog generation during software deployment?

Automated changelog generation is needed during software deployment to document version changes. It extracts details from Conventional Commits to create an accurate release history alongside SemVer tagging.