gaia-publish

Automate non-deployable project releases with a five-step orchestrator and CI checks.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/gaiastudio-ai/gaia-framework --skill gaia-publish-gaiastudio-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gaia-publish
Source: https://github.com/gaiastudio-ai/gaia-framework/tree/main/plugins/gaia/skills/gaia-publish
Command: npx skills add https://github.com/gaiastudio-ai/gaia-framework --skill gaia-publish-gaiastudio-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the release process for non-deployable projects, ensuring a consistent and controlled release workflow without auto-retry or auto-rollback features.

Core Features & Use Cases

  • Release Automation: Execute a five-step orchestrator to manage release stages (pre-publish gate, manifest version check, trigger publish, post-publish verify, final verdict).
  • CI Integration: Verifies required CI checks are green on the source branch before proceeding.
  • Version Matching: Ensures the manifest version matches the specified version.
  • Adapter Dispatch: Resolves and dispatches the appropriate adapter for the distribution channel.
  • Verification: Performs post-publish verification against the registry to confirm the release.

Quick Start

To publish a version of your project, run: /gaia-publish --version <semver> [--dry-run] [--skip-verify] [--strict-builtin]

Frequently Asked Questions about gaia-publish

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

FAQPage Schema
How do I automate release workflows for non-deployable projects?▼

You can automate release workflows for non-deployable projects by executing a five-step orchestrator that handles pre-publish gating, version matching, adapter dispatch, and post-publish registry verification.

What is the best way to integrate CI checks into an automated release process?▼

The best way to integrate CI checks is to use a release automation tool that verifies required CI checks are green on the source branch before proceeding to trigger the publish step.

Do I need to install gh and jq to manage project releases?▼

Yes, you need to install gh and jq. These dependencies are required to run the release automation orchestrator and execute its custom or built-in distribution channel adapters.

Can I skip registry verification when running a release automation workflow?▼

Yes, you can skip registry verification by running the publish command with the --skip-verify flag, which bypasses the post-publish verification step against the registry.

Does this release automation tool support auto-rollback on failure?▼

No, this release automation tool does not support auto-rollback or auto-retry features, ensuring a consistent and controlled release workflow where failures must be handled manually.

Can I test a release automation workflow before publishing to a distribution channel?▼

Yes, you can test the workflow by running the publish command with the --dry-run flag, allowing you to simulate the release process without deploying to the distribution channel.