gh-oss-release

Automates multi-repo release management with gh oss-watch and semver bumping.

15|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/jackchuka/skills --skill gh-oss-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-oss-release
Source: https://github.com/jackchuka/skills/tree/main/gh-oss-release
Command: npx skills add https://github.com/jackchuka/skills --skill gh-oss-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Batch release management across multiple OSS repositories by checking release status with gh oss-watch releases and proposing appropriate semver bumps.

Core Features & Use Cases

  • Checks release status across repos and identifies unreleased commits.
  • Analyzes commits to determine the correct semver bump and suggests the highest applicable upgrade.
  • Confirms with the user before creating releases and supports optional post-release steps (e.g., updating a Homebrew tap).

Quick Start

Execute the release workflow to check statuses, propose bumps, and create releases for all tracked repositories.

Frequently Asked Questions about gh-oss-release

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

FAQPage Schema
How do I automate batch release management across multiple GitHub repositories?

Automate batch release management by checking unreleased commits across multiple GitHub repositories with gh oss-watch, proposing appropriate semver bumps, and creating releases after user confirmation. The workflow analyzes commit history to determine the correct version upgrade for each tracked repository.

How does semantic versioning work when releasing multiple OSS repositories?

Semantic versioning for multiple OSS repositories works by analyzing unreleased commits per repository to determine the correct semver bump, suggesting the highest applicable upgrade based on commit content, and prompting for user confirmation before creating the releases.

Do I need the gh CLI and oss-watch extension to coordinate multi-repo GitHub releases?

Yes, coordinating multi-repo GitHub releases requires the gh CLI and the gh oss-watch extension. These dependencies enable checking release status across repositories, analyzing unreleased commits, and proposing appropriate semver bumps for batch release creation.

Can I push GitHub releases to a Homebrew tap after creating them?

Yes, you can push GitHub release results to a Homebrew tap after confirmation. The batch release workflow supports optional post-release steps, including updating a Homebrew tap once the releases are created across the tracked repositories.

What's the best way to check unreleased commits across multiple OSS repositories?

The best way to check unreleased commits across multiple OSS repositories is using the gh oss-watch releases command, which identifies pending commits and proposes appropriate semver bumps for batch release coordination.

Why does batch release management require user confirmation before creating releases?

Batch release management requires user confirmation before creating releases to ensure the proposed semver bumps accurately reflect the unreleased commits analyzed per repository, preventing unintended version upgrades across multiple tracked repositories.