GAIA Docker Release Management

VerifiedSafe

Manages releases for GAIA Docker containers. Reads current versions from VERSION.json, supports bumping versions for gaia-linux or gaia-dev with automatic file updates, or re-triggering the publish workflow.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#release-management#docker#versioning#ci

Recommended for

Automated summary

Manages Docker container releases by bumping versions in configuration and documentation files, and re-triggering CI workflows.

Strengths

  • Automates version bumps across multiple files simultaneously
  • Reduces manual errors during releases
  • Integrates with GitHub Actions for deployment
  • Provides clear step-by-step guidance

Limitations

  • Only works with a specific project structure (GAIA)
  • Requires proper setup of VERSION.json and README files
  • Does not handle branch conflicts or complex tagging
When to use it

When releasing new versions of Docker containers in a standardized project with VERSION.json and dedicated README files.

When not to use it

For projects without a VERSION.json file or when releases require advanced branching or tagging.

Security analysis

Safe
Quality score92/100

The skill only reads version files and updates them with user-supplied version numbers; the only command that interacts with external systems is 'gh workflow run', which triggers a predefined CI workflow and does not run arbitrary destructive commands or exfiltrate data.

No concerns found

How this analysis is made

Examples

Trigger release workflow
/release
<release-skill> # Release Skill

Manage releases for GAIA Docker containers.

Usage

/release

Workflow

  1. Read current versions from VERSION.json
  2. Ask user for action:
    • New Release: Bump version for gaia-linux, gaia-dev, or both
    • Re-trigger Workflow: Re-publish current versions to Docker Hub
  3. For New Release:
    • Ask which container(s) to release
    • Ask for new version number(s)
    • Update VERSION.json
    • Update hardcoded versions in README files
    • Commit and push changes
  4. For Re-trigger:
    • Run gh workflow run to re-publish

Instructions

When the user invokes /release:

Step 1: Read Current State

Read VERSION.json to get current versions:

cat VERSION.json

Step 2: Ask User Intent

Use AskUserQuestion to ask:

  • "What would you like to do?"
    • New gaia-linux release - Bump gaia-linux version
    • New gaia-dev release - Bump gaia-dev version
    • Re-trigger workflow - Re-publish current versions

Step 3a: For New Release

If user chose new release:

  1. Ask for the new version number
  2. Update VERSION.json with the new version
  3. Update version references in these files:
    • docs/gaia-linux/README.md - Update all occurrences of the old version
    • docs/gaia-dev/README.md - Update all occurrences of the old version
    • README.md - Update version in "Current Versions" line and examples
  4. Commit changes with message: Release <container> v<version>
  5. Push to main branch

Step 3b: For Re-trigger

If user chose re-trigger:

gh workflow run "Test, Publish, Release" --ref main

Then inform user that the workflow has been triggered and they can check progress at the Actions tab.

Files to Update on New Release

For gaia-linux release:

  • VERSION.json - Update "gaia-linux" value
  • docs/gaia-linux/README.md - Replace all gaia-linux:<old> with gaia-linux:<new>
  • README.md - Update "Current Versions" line and docker examples

For gaia-dev release:

  • VERSION.json - Update "gaia-dev" value
  • docs/gaia-dev/README.md - Replace all gaia-dev:<old> with gaia-dev:<new>
  • README.md - Update "Current Versions" line and docker examples

Example Interaction

User: /release

Claude: Current versions:
- gaia-linux: 0.15.3
- gaia-dev: 1.0.0

What would you like to do?
[New gaia-linux release] [New gaia-dev release] [Re-trigger workflow]

User: New gaia-linux release

Claude: What version should gaia-linux be released as?
Current: 0.15.3

User: 0.15.4

Claude: I'll update the following:
- VERSION.json: gaia-linux → 0.15.4
- docs/gaia-linux/README.md: Update version references
- README.md: Update version references

[Makes changes, commits, and pushes]

Done! Release v0.15.4 has been pushed. The CI workflow will:
1. Run tests
2. Build and push Docker images
3. Update Docker Hub README
4. Create GitHub release

Check progress: https://github.com/<repo>/actions
</release-skill>

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/gaia-docker-release-management-mmk3ni40/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/gaia-docker-release-management-mmk3ni40' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/gaia-docker-release-management-mmk3ni40/download' --output '.skill-downloads/gaia-docker-release-management-mmk3ni40/SKILL.md.part' && mv '.skill-downloads/gaia-docker-release-management-mmk3ni40/SKILL.md.part' '.skill-downloads/gaia-docker-release-management-mmk3ni40/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/gaia-docker-release-management-mmk3ni40/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills