release

Coordinate release verification gates and report readiness before shipping.

44|5|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/Mburdo/knowledge_and_vibes --skill release-mburdo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Mburdo/knowledge_and_vibes/tree/main/.claude/skills/release
Command: npx skills add https://github.com/Mburdo/knowledge_and_vibes --skill release-mburdo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release readiness is critical to prevent shipping unfinished or unsafe code. This Skill provides a formal gate that verifies all work is complete, security checks pass, tests run, and release artifacts are ready for production.

Core Features & Use Cases

  • Final verification: ensures all beads are closed, no in_progress work, and the release process is ready to proceed.
  • Security and quality gates: runs mandatory security scans, test suites, and code-state checks to validate production readiness.
  • Multi-agent coordination: coordinates release communications, reservations, and status reporting to stakeholders via Agent Mail and release reports.

Quick Start

Run the release checklist after all beads are closed and before production deployment.

Frequently Asked Questions about release

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

FAQPage Schema
How do I verify release readiness before shipping code to production?

Release readiness is verified by enforcing bead closure, running mandatory security scans, executing test suites, and checking git state to ensure no in_progress work remains before production deployment.

What is a pre-production verification gate and how does it work?

A pre-production verification gate coordinates security scans, test execution, and git state checks across codebases to validate that all work is complete and release artifacts are safe for production.

Can I automate CI/CD security scans and test execution for multi-agent release streams?

Yes, this Skill automates CI/CD security scans and test execution while coordinating multi-agent release streams, using Agent Mail to manage reservations and report status to stakeholders.

How do I enforce bead closure and block incomplete work from reaching production?

You enforce bead closure by running a release checklist that verifies no in_progress work exists, mandatory security scans pass, and all tests execute successfully before proceeding to deployment.

What's the best way to coordinate release communications across multiple agents?

Multi-agent release coordination is handled through Agent Mail, which manages release communications, reservations, and status reporting to operators and stakeholders during the verification process.

When should I run a release verification checklist in my deployment workflow?

Run the release checklist after all beads are closed and before production deployment to ensure security gates pass, tests execute, and git state validates production readiness.