release-manager

Orchestrate BenchFlow release lifecycle with versioning, channel distribution, and pre-tag audit gates.

317|40|Updated Jan 21, 2025
One-click install
npx skills add https://github.com/benchflow-ai/benchflow --skill release-manager-benchflow-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-manager
Source: https://github.com/benchflow-ai/benchflow/tree/main/.agents/skills/release-manager
Command: npx skills add https://github.com/benchflow-ai/benchflow --skill release-manager-benchflow-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the risk of human error in software releases by enforcing strict audit gates, channel-specific versioning, and automated verification for BenchFlow releases.

Core Features & Use Cases

  • Channel Management: Safely distinguishes between public PyPI releases, internal dev previews, and release candidates.
  • Automated Audit Gates: Enforces CI checks, e2e live smoke tests, and structural adversarial audits before tagging.
  • Use Case: When preparing a new version, use this skill to ensure the release branch is correctly staged, the CHANGELOG is accurate, and all security and integrity gates are passed before pushing a public tag.

Quick Start

Ask the release manager to guide you through the pre-tag audit gates and versioning steps for the upcoming release candidate.

Frequently Asked Questions about release-manager

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

FAQPage Schema
How do I automate pre-tag audit gates for a PyPI deployment?

Pre-tag audit gates for a PyPI deployment are automated by enforcing strict CI checks, e2e live smoke tests, and structural adversarial audits before tagging a release candidate.

What is the safest way to manage versioning across internal preview channels and public releases?

Safe versioning across internal preview channels and public releases is managed by distinguishing channel-specific distribution paths, ensuring release candidates are correctly staged before pushing a public tag.

How do I ensure my CHANGELOG is accurate before pushing a public tag?

Ensuring an accurate CHANGELOG before pushing a public tag is handled by the pre-tag audit process, which verifies the release branch is correctly staged and structural integrity gates are passed.

Does CI/CD integration work with automated release orchestration?

CI/CD integration works directly with release orchestration by satisfying requirements for hardened verification and automating the end-to-end release lifecycle from staging to deployment.

When do I need an adversarial audit for software release candidate testing?

An adversarial audit for release candidate testing is needed when preparing a new version to eliminate human error and satisfy hardened verification requirements before a public deployment.