release

Automate the end-to-end Gemini Voyager release process from triage to GitHub release assembly.

19.3k|639|Updated Oct 4, 2025
One-click install
npx skills add https://github.com/Nagi-ovo/gemini-voyager --skill release-nagi-ovo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Nagi-ovo/gemini-voyager/tree/main/.claude/skills/release
Command: npx skills add https://github.com/Nagi-ovo/gemini-voyager --skill release-nagi-ovo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Orchestrates a multi-step software release workflow for Gemini Voyager, reducing manual toil and the risk of shipping errors.

Core Features & Use Cases

  • Open-issue triage, preflight checks, version bump, 10-locale changelog, commit, tag, push, curated GitHub release body, and packaging Chrome/Firefox artifacts.
  • Optional Edge compatibility zip and Safari DMG flows, with proper handling of Edge and Safari-specific steps.
  • Use case: When preparing a new Gemini Voyager release, trigger the entire process from issue triage to release publication, including changelog localization.

Quick Start

Ask me to release a new Gemini Voyager version and I will start the full release workflow from pre-flight to release publication.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate a GitHub release workflow with version bumps and changelogs?

Yes, packaging browser extension artifacts is supported for Chrome and Firefox. The workflow also includes optional flows to package Edge compatibility ZIP files and Safari DMG files across different locales.

What's the best way to generate a localized changelog for a new release?

Pre-flight validation for an automated release includes running typechecks, linters, and tests. These checks execute automatically before version bumping to ensure code stability and reduce the risk of shipping errors.

How do I publish a new version of a browser extension from start to finish?

Yes, packaging browser extension artifacts is supported for Chrome and Firefox. The workflow also includes optional flows to package Edge compatibility ZIP files and Safari DMG files across different locales.

Does automated release automation support packaging artifacts for Chrome, Firefox, and Edge?

Pre-flight validation for an automated release includes running typechecks, linters, and tests. These checks execute automatically before version bumping to ensure code stability and reduce the risk of shipping errors.

What pre-flight checks are required before bumping a version and pushing a tag?

Generating a localized changelog is best handled by an automated release workflow that compiles release notes across multiple locales. It updates manifest files and integrates localization notes directly into the curated GitHub release body.