release

Orchestrate a multi-step software release for claude-trace with SemVer compliance.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/agentglass/claude-trace --skill release-agentglass
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/agentglass/claude-trace/tree/main/.claude-plugin/skills/release
Command: npx skills add https://github.com/agentglass/claude-trace --skill release-agentglass

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a robust, step-by-step process to ensure safe and consistent software releases, preventing common errors that lead to incidents.

Core Features & Use Cases

  • Guided Release Workflow: Executes a precise 11-step sequence for cutting new releases.
  • Automated Verification: Includes checks for CI status, security advisories, and test suite results.
  • Version Management: Manages version bumping across multiple project files (Cargo.toml, pyproject.toml, package.json, .claude-plugin/plugin.json).
  • Artifact Building & Publishing: Orchestrates the build of release artifacts and their publication to PyPI and npm.
  • Use Case: A developer needs to release a new version of the claude-trace library. This skill guides them through verifying CI, updating versions, running tests, building artifacts, tagging, and publishing to package managers.

Quick Start

Initiate the release process for the project by typing "release".

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate software versioning and publishing to PyPI and npm?

Automate software versioning and publishing by executing a guided release workflow that bumps versions across configuration files, runs CI checks, builds artifacts, and publishes to PyPI and npm.

How does a CI/CD pipeline ensure safe SemVer version bumping across multiple project files?

Safe SemVer version bumping is ensured by synchronizing version updates across files like Cargo.toml, pyproject.toml, and package.json, followed by automated security advisories and test suite verification.

What is the process for building Python wheels and WASM packages for a release?

Building Python wheels and WASM packages involves an automated sequence that runs comprehensive checks, compiles the artifacts, creates signed Git tags, and prepares the packages for publication.

What happens if a deployment fails during an automated release process?

If a deployment fails, the automated release process includes predefined rollback procedures to revert changes and restore the repository to its previous stable state.

Do I need to manually run security checks before publishing a version?

Manual security checks are not required because the release workflow executes automated verification for CI status, security advisories, and test suite results before building artifacts.

Can I use this release automation for initializing a post-release development cycle?

Yes, the release automation includes post-release development cycle preparation to seamlessly transition the repository into the next development phase after publishing.