agentplane-release-and-packaging-operator

Manage Agentplane package releases with version parity and publication verification.

72|9|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/basilisk-labs/agentplane --skill agentplane-release-and-packaging-operator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentplane-release-and-packaging-operator
Source: https://github.com/basilisk-labs/agentplane/tree/main/skills/agentplane-release-and-packaging-operator
Command: npx skills add https://github.com/basilisk-labs/agentplane --skill agentplane-release-and-packaging-operator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the complexity of managing multi-package releases, ensuring version parity, and verifying publication integrity across npm, GitHub, and container registries.

Core Features & Use Cases

  • State-Machine Release Management: Treats releases as a series of verifiable states rather than linear scripts, preventing partial or broken deployments.
  • Automated Verification: Performs rigorous checks on package build order, npm version availability, and provenance evidence.
  • Use Case: When preparing a new version of the Agentplane CLI and its associated core packages, use this skill to validate build order, ensure all packages are published with correct provenance, and confirm successful installation via smoke tests.

Quick Start

Use the agentplane-release-and-packaging-operator skill to validate the current release state and prepare the next version bump for the repository.

Frequently Asked Questions about agentplane-release-and-packaging-operator

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

FAQPage Schema
How do I automate multi-package npm releases with version parity?

Verifying npm package provenance involves checking build order and registry publication evidence. This skill performs rigorous automated checks on npm version availability and provenance evidence to ensure reproducible and secure release artifacts across registries.

What do I need to set up before automating GitHub release workflows?

Automating GitHub release workflows requires local Git state, Bun runtime, and registry access. You need these environment dependencies configured before initiating the release lifecycle to ensure reproducible builds and secure release evidence generation.

How does state-machine release management prevent broken npm deployments?

The best way to handle cross-platform artifact auditing is treating releases as verifiable states with automated checks. This skill validates package build order, npm version availability, and provenance evidence to ensure publication integrity across npm, GitHub, and container registries.

Why does my multi-package release fail during publication verification?

Multi-package release publication verification fails when version parity or build ordering checks detect discrepancies. This skill prevents partial deployments by rigorously validating package build order, npm version availability, and provenance evidence before completing the release lifecycle.