Overview

Prepare and validate OpenSkills release readiness across runtime, bindings, examples, and regression gates using a deterministic checklist. It delivers a go/no-go decision to ensure publish readiness.

How This Skill Works

The process enforces a structured gate sequence: verify runtime with cargo check and cargo test for openskills-runtime, build bindings for TS and Python, confirm example-agent sanity checks, and ensure changelog/version consistency plus packaging prerequisites. The final Go/No-Go decision surfaces explicit blockers and exact repro commands.

When to Use It

• Preparing a release candidate
• Validating publish readiness before publishing
• Freezing code and validating all gates
• Verifying binding builds (TS and Python)
• Documenting blockers and rollback notes

Quick Start

1. Step 1: Run core verification: cargo check -p openskills-runtime and cargo test -p openskills-runtime
2. Step 2: Validate all gates: runtime, bindings (TS/Python), examples, changelog/version, packaging prerequisites
3. Step 3: Decide GO/NO-GO and document blockers with exact repro commands

Best Practices

• Automate gate runs and collect outputs for repeatability
• Keep changelog and version pins aligned with releases
• Record any skipped gates with explicit reasons
• Capture explicit blockers and exact repro commands
• Summarize runtime: cargo check/test outputs to prove status

Example Use Cases

• Release candidate for v1.2.0 passes all gates: GO
• TS binding build fails; NO-GO with blockers and repro commands
• Changelog/version mismatch detected; NO-GO with rollback notes
• Known flaky tests lead to skipped gates; GO with risks documented
• Packaging prerequisites incomplete; NO-GO until prerequisites are met

Frequently Asked Questions