gaia-release

Automate and validate Gaia release pipelines across local and CI environments.

3|1|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/metraton/gaia --skill gaia-release-metraton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gaia-release
Source: https://github.com/metraton/gaia/tree/main/skills/gaia-release
Command: npx skills add https://github.com/metraton/gaia --skill gaia-release-metraton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gaia release management streamlines testing, validation, and publishing of Gaia releases across local and CI environments.

Core Features & Use Cases

  • Supports live, dry-run, beta, and release modes to validate packaging, sandbox installation, and artifact quality.
  • Automates end-to-end release validation including build checks, npm pack, sandbox install, and post-install checks.
  • Use case: When preparing a Gaia update, run the dry-run to ensure the install flow will succeed in production.

Quick Start

Run the dry-run flow to validate the Gaia release pipeline in a clean sandbox.

Frequently Asked Questions about gaia-release

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

FAQPage Schema
How do I validate a release pipeline before publishing changes to production?

You can validate a release pipeline before production by running a dry-run flow in a clean sandbox. This process verifies build checks, packaging, and sandbox installation to ensure artifacts meet distribution standards without publishing.

What is the best way to automate Gaia release testing across local and CI environments?

The best way to automate Gaia release testing is to use a coordinated pipeline that applies dry-run, beta, and release modes. This automates end-to-end validation including build verification and post-install checks across local and CI environments.

Can I test sandbox installation and artifact quality for a beta release?

Yes, you can test sandbox installation and artifact quality for a beta release. The beta mode validates the packaging and sandbox install flow to ensure your changes are stable before the final release.

Do I need build verification before running a dry-run for packaging?

Yes, build verification is required before running a dry-run for packaging. The release process mandates build checks, npm pack, sandbox installation, and post-install checks to ensure all artifacts meet distribution standards.

Why does my release pipeline fail post-install checks in the sandbox?

Release pipelines fail post-install checks in the sandbox when artifacts do not meet distribution standards. You must ensure build verification and packaging succeed first, applying the correct security or operator mode during installation.

Does Gaia release testing support both operator and security modes?

Yes, Gaia release testing supports both operator and security modes. You can validate testing and publishing changes across local, sandbox, and CI environments using either mode to ensure comprehensive release coverage.