gh-oss-release
Create GitHub releases across multiple OSS repositories. Checks release status via `gh oss-watch releases`, analyzes unreleased commits to recommend semver bumps, confirms with user, then creates releases. Triggers: "create releases", "release my packages", "check for releases", "oss releases", "gh oss-watch releases", "/oss-release", "release status", "bump versions"
Best use case
gh-oss-release is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create GitHub releases across multiple OSS repositories. Checks release status via `gh oss-watch releases`, analyzes unreleased commits to recommend semver bumps, confirms with user, then creates releases. Triggers: "create releases", "release my packages", "check for releases", "oss releases", "gh oss-watch releases", "/oss-release", "release status", "bump versions"
Teams using gh-oss-release should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/gh-oss-release/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How gh-oss-release Compares
| Feature / Agent | gh-oss-release | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create GitHub releases across multiple OSS repositories. Checks release status via `gh oss-watch releases`, analyzes unreleased commits to recommend semver bumps, confirms with user, then creates releases. Triggers: "create releases", "release my packages", "check for releases", "oss releases", "gh oss-watch releases", "/oss-release", "release status", "bump versions"
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# OSS Release
Batch release workflow for multiple OSS repositories using `gh oss-watch releases`.
## Workflow
### Step 1: Check Release Status
Run `gh oss-watch releases` to identify repos with unreleased commits.
If all repos are up to date, report that and stop.
### Step 2: Analyze Unreleased Commits
For each repo needing a release, fetch commit messages since the last tag in parallel:
```bash
gh api repos/<owner>/<repo>/compare/<last-tag>...HEAD --jq '[.commits[] | .commit.message | split("\n")[0]] | .[]'
```
### Step 3: Recommend Semver Bump
Classify each commit's first line and recommend the highest applicable bump:
| Commit pattern | Bump |
| ------------------------------------------------------- | --------- |
| `deps:`, `deps-dev:`, `ci:`, `chore:`, maintenance-only | **patch** |
| `feat:`, new functionality, non-breaking additions | **minor** |
| `BREAKING CHANGE`, `!:` suffix, API removals | **major** |
If ALL commits are deps/ci/chore, recommend **patch**. If any commit adds a feature, recommend **minor**. If any commit has breaking changes, recommend **major**.
### Step 4: Present Recommendations
Present a table for user confirmation:
```
| Repo | Current | Recommended | Commits | Rationale |
|------|---------|-------------|---------|-----------|
| repo-name | v1.2.3 | v1.2.4 | 5 | All dependency bumps |
```
Use AskUserQuestion or wait for explicit user confirmation before proceeding.
### Step 5: Create Releases
After confirmation, create releases in parallel:
```bash
gh release create <new-tag> --repo <owner>/<repo> --generate-notes
```
### Step 6: Verify
Run `gh oss-watch releases` again to confirm all repos show "up to date".
### Step 7: Wait for Release Builds
Before updating the homebrew tap, all tag-triggered CI builds must complete successfully so release artifacts exist for formula updates.
Check the most recent run for each released repo in parallel:
```bash
gh run list --repo <owner>/<repo> --limit 3
```
If any run is still `in_progress` or `queued`, wait for it to complete:
```bash
gh run watch <run-id> --repo <owner>/<repo> --exit-status
```
If any build fails, stop and surface the failure to the user — do not proceed to the tap update.
### Step 8: Update Homebrew Tap
Ask the user if they want to update the homebrew tap before proceeding. If they decline, stop here.
After confirmation, trigger the scheduled workflow which handles formula updates automatically:
```bash
gh workflow run scheduled.yml --repo jackchuka/homebrew-tap
```
## Important Notes
- **Tag-triggered CI**: Most repos have CI that triggers on tag push (goreleaser, gh-extension-precompile, npm publish). The `gh release create` command creates the tag which triggers the CI build.
- **npm packages with tag-triggered workflows**: These repos derive version from the git tag during CI — no package.json bump needed.
- **Parallel execution**: Fetch commits and create releases in parallel across repos for speed.
- **Never force**: Always confirm with user before creating any releases.Related Skills
gh-oss-release-prep
Systematic OSS release preparation checklist. Use when preparing a repository for open-source publishing, making a project public, or ensuring a repo meets OSS standards. Triggers: "prepare for OSS", "ready to publish", "make this public", "OSS checklist", "scan repo for publish", "open source this", "/oss-release-prep"
restaurant-search
Search for Japanese restaurants using the `hpp` CLI (HotPepper Gourmet API). Use when the user wants to find a restaurant, plan a dinner, search for izakayas, or book a group meal in Japan. Triggers on requests like "find a restaurant near Shibuya", "search for izakayas in 新宿", "restaurant for 10 people in 浜松町", "dinner spot near Tokyo station".
project-namer
Use when naming a project, repository, tool, or product and wanting a memorable, unique name
p-slack-triage
Scan Slack for messages needing your attention, walk through them one-by-one, and draft/send replies. Covers DMs, mentions, threads, and channel activity. Use when the user wants to triage Slack, check what needs attention, or draft replies. Triggers on "triage slack", "check slack", "what needs my attention on slack", "slack replies", "review slack messages", "/slack-triage".
p-news-briefing
Use when the user asks for news, wants a briefing, says "/news-briefing", or asks to aggregate recent information on any topic. Triggers on requests like "what's happening with AI", "get me news on crypto", "news briefing on climate".
p-md-to-slides
Convert a structured Markdown deck source into a styled Google Slides presentation. Use this skill when the user has a slide.md file (or wants to write one) and wants Google Slides output — talks, LT decks, lecture slides, conference presentations, internal explainers. Trigger phrases include "md からスライド作って", "slide.md を Google Slides にして", "発表資料を Google Slides で", "convert this markdown to slides", "build a Google Slides deck from this markdown", "make slides from md", "/md-to-slides", and similar. Also use when the user references a presentation/<date>/slide.md file structure with `## Slide N — title`, `**話すこと:**`, and `**スライド要素:**` sections.
p-ego-search
Search for mentions of you across Slack, Fireflies, and GitHub. Triggers on "egosearch", "/egosearch", "search for mentions of me", "who's talking about me".
p-daily-standup
Aggregate previous business day activity and post standup update to Slack. Use when the user says "standup", "daily standup", "post status", "status update", or "/daily-standup".
p-daily-report
Use when reviewing what you worked on, creating standups, writing status updates, tracking daily/weekly progress, or asking "what did I do today"
p-daily-reflection
Reflect on past work and iterate to improve. Analyzes Claude sessions, GitHub, Slack, and Fireflies to generate a journal entry with actionable improvements. Updates persistent memory with confirmed learnings. Use when the user says "reflect", "reflection", "what can I improve", "retrospective", "review my work", or "/daily-reflection".
p-blog-writer
Write blog posts in {user_name}'s voice with theoretical depth and persuasive arguments. Iterative workflow: intake → outline → section-by-section expansion → polish. Adapts to tool announcements, opinion pieces, deep-dives, and tutorials. Use when the user says "/blog-writer", "write a blog post", "draft an article about", "help me write about", or wants to create blog content.
p-blog-post-mining
Mine development activities for blog-worthy topics and create outlines. Analyzes Claude session history, GitHub commits/PRs, Slack discussions, and Fireflies meeting recordings to find interesting stories. Use when the user wants blog ideas, content inspiration, or asks "what can I write about", "find blog material", "blog ideas from my work", "/blog-post-mining".