release

Automate SDLC-compliant release workflows across multiple project types with validation checks.

3|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/zircote/agents --skill release-zircote
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/zircote/agents/tree/main/skills/release
Command: npx skills add https://github.com/zircote/agents --skill release-zircote

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual, error-prone release processes across multi-type projects create delays and risk. The Release Skill coordinates comprehensive SDLC validation to ensure only well-tested, secure code is released.

Core Features & Use Cases

  • Automated detection of project type (Claude Plugin, Python, Node.js, Go, Rust).
  • End-to-end release validation including tests, lint, security, coverage, and changelog checks.
  • Optional dry-run and PR-based release workflows with conventional commits guidance.
  • Example: release a patch across all affected components in a monorepo and publish tags.

Quick Start

Invoke the release workflow with a target release type (patch/minor/major) and follow prompts to complete the release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate release validation across multiple project types like Python and Node.js?

Automated release validation detects project types like Python, Node.js, Go, and Rust to coordinate tests, lint, coverage, and security checks. It ensures only well-tested, secure code is published by enforcing SDLC compliance across repositories.

Can I run a dry-run release workflow before publishing to check for breaking changes?

Yes, you can execute a dry-run release workflow to validate checks before publishing. It identifies breaking changes, verifies changelog updates, and runs security validations without creating tags or publishing artifacts.

What is the best way to coordinate patch releases across components in a monorepo?

Coordinating patch releases in a monorepo requires detecting affected components and applying conventional commits guidance. This workflow automates validation, generates changelogs, detects breaking changes, and publishes tags across all impacted project types.

Does this release automation handle CI configuration checks and changelog generation?

Release automation handles CI configuration checks and changelog generation as part of its core validation. It runs tests, lint, and security validations while ensuring changelogs are updated and CI configurations comply with SDLC requirements.

Do I need conventional commits to automate versioning for Go and Rust projects?

Using conventional commits provides guidance for automated versioning across Go and Rust projects. The workflow detects project types, applies version bumps, and validates changes to ensure releases comply with SDLC standards.

When should I use a PR-based release workflow instead of a direct publish?

A PR-based release workflow should be used when you need review and validation before publishing. It runs tests, lint, security, and breaking changes detection within a pull request to ensure code quality before merging and releasing.