Our review
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 releasing new versions of Docker containers in a standardized project with VERSION.json and dedicated README files.
For projects without a VERSION.json file or when releases require advanced branching or tagging.
Security analysis
SafeThe 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
Examples
/releaseManage releases for GAIA Docker containers.
Usage
/release
Workflow
- Read current versions from
VERSION.json - 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
- 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
- For Re-trigger:
- Run
gh workflow runto re-publish
- Run
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:
- Ask for the new version number
- Update
VERSION.jsonwith the new version - Update version references in these files:
docs/gaia-linux/README.md- Update all occurrences of the old versiondocs/gaia-dev/README.md- Update all occurrences of the old versionREADME.md- Update version in "Current Versions" line and examples
- Commit changes with message:
Release <container> v<version> - 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"valuedocs/gaia-linux/README.md- Replace allgaia-linux:<old>withgaia-linux:<new>README.md- Update "Current Versions" line and docker examples
For gaia-dev release:
VERSION.json- Update"gaia-dev"valuedocs/gaia-dev/README.md- Replace allgaia-dev:<old>withgaia-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>Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.