gaia-release

Automates the GAIA release workflow from notes drafting through tagging, publishing, and announcement.

1.6k|168|Updated Dec 16, 2024
One-click install
npx skills add https://github.com/amd/gaia --skill gaia-release-amd
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: gaia-release
Source: https://github.com/amd/gaia/tree/main/.claude/skills/gaia-release
Command: npx skills add https://github.com/amd/gaia --skill gaia-release-amd

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes references (resource) components.

What problem does it solve? Cutting a GAIA release involves many error-prone manual steps β€” drafting release notes, opening a release PR, verifying the merged commit, pushing a tag, monitoring the publish pipeline, and writing the Discord announcement β€” where a single mistake (like a reverted version bump or an unescaped MDX character) can break the release. ## Core Features & Use Cases - Phased release checklist with hard gates: Six phases (notes, PR, pre-tag verification, tag, publish monitoring, announcement) each pause for explicit user approval before any irreversible action like pushing a tag. - Resume detection: Re-invocation safe β€” inspects git tags, PRs, and GitHub releases to detect where a multi-day release flow left off and resumes at the correct phase. - House-style release notes: Enforces a strict bulleted, plain-language notes format with word budgets, MDX escaping for the changelog, and validation via validate_release_notes.py plus mintlify validate. - Use Case: A maintainer says "release v0.17.5" and the skill drafts the notes, opens the release PR, verifies the merged commit builds green, pushes the annotated tag, watches the publish workflow, and drafts the Discord announcement β€” stopping at every gate for approval. ## Quick Start Ask the assistant to cut a GAIA release for a specific version, for example: "Release v0.17.5 using the gaia-release skill."

Frequently Asked Questions about gaia-release

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

FAQPage Schema
How do I cut a GAIA release with this skill?β–Ό

Invoke the skill with a target version like "release v0.17.5" or no argument to auto-suggest the next patch from src/gaia/version.py. It walks through six gated phases: notes, PR, pre-tag verification, tag, publish monitoring, and announcement.

How does the skill handle resuming an interrupted release?β–Ό

Before any phase, it checks git tags, open and merged PRs, and existing GitHub releases to detect current state. Based on a resume table, it skips completed phases and announces where it is resuming, never overwriting merged notes.

What release notes format does the skill enforce?β–Ό

Notes are bulleted, plain, and factual with sections for Breaking Changes, What's New, Bug Fixes, Known Issues, Contributors, and Full Changelog. A word budget caps narrative content at 350 words for patches and 600 for minor or major releases, validated by script.

Why does the skill require pre-tag verification before pushing a tag?β–Ό

The v0.17.4 release shipped two blocking bugs that merged-PR CI missed: a squash-merge silently reverting version.py and a circular pip install dependency in the AppImage smoke test. Phase 3 re-verifies the version and runs Build Installers on the merged commit before tagging.

Can the skill push tags or post Discord announcements automatically?β–Ό

No. Pushing tags, approving the publish environment gate, and posting to Discord all require explicit human action. The skill surfaces URLs and drafts, then stops and waits for confirmation at each irreversible step.

What happens if the publish workflow fails partway through?β–Ό

On transient flake like a timeout, the skill reruns only failed jobs with gh run rerun --failed. On real failures it stops and surfaces the failing step and logs, and never deletes or re-pushes a tag.