How do I install the Publish Github Release skill?

Run npx skillmds@latest add imbhargav5/publish-github-release in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Publish Github Release safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Publish Github Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Publish Github Release free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Publish Github Release?

imbhargav5 (@imbhargav5) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Publish Github Release by imbhargav5

Name: Publish Github Release
Author: imbhargav5

Publish Github Release

Prepare an Open Recorder GitHub release by choosing a patch, minor, or major version bump, dispatching the release PR workflow, and guiding the user through merging that PR so the actual release can publish. Use when the user asks to cut, ship, dispatch, or publish a GitHub release, or to bump the app version for a release.

imbhargav5 d8c07a9 2 files · 7.1 KB Updated Sep 17, 2026

File contents

Publish GitHub Release

Use this skill when the user wants to publish an Open Recorder release from this repository.

Quick start

Pick the script that matches the release type:

pnpm release:patch
pnpm release:minor
pnpm release:major

If the user wants to choose interactively, use:

pnpm release:dispatch

Preconditions

Before running a release command:

Make sure the repo is on the branch the user wants to release from.
Make sure gh auth status succeeds.
If this release needs signed macOS artifacts and secrets are not configured yet, run:

pnpm release:setup-macos-signing

Release type guidance

patch: bug fixes, small polish, or safe maintenance updates.
minor: new backward-compatible features.
major: breaking changes or compatibility resets.

Useful command patterns

You can pass extra flags through pnpm with --:

pnpm release:patch -- --notes "Bug fixes and stability improvements"
pnpm release:minor -- --name "Open Recorder v1.4.0" --yes
pnpm release:major -- --latest false

Supported flags come from scripts/dispatch-release-build.mjs:

--notes VALUE
--name VALUE
--latest true|false
--yes
--ref VALUE
--repo OWNER/REPO

What the skill should do

Confirm the intended release type if the user did not already specify patch, minor, or major.
Check the preconditions above.
Run the matching root package script.
Report that the release PR workflow was dispatched and explain that GitHub Actions will calculate the next version and open or update the release PR.
If the user asks how the release process works or something fails, read references/release-process.md.

Important behaviors

The local dispatcher does not update version files or create commits in the user's checkout.
It dispatches .github/workflows/release-pr.yml, and that workflow computes the next version and opens or updates the release PR.
Merging the release PR triggers .github/workflows/release.yml, which builds and publishes the actual GitHub release.

---name: publish-github-releasedescription: Prepare an Open Recorder GitHub release by choosing a patch, minor, or major version bump, dispatching the release PR workflow, and guiding the user through merging that PR so the actual release can publish. Use when the user asks to cut, ship, dispatch, or publish a GitHub release, or to bump the app version for a release.---# Publish GitHub ReleaseUse this skill when the user wants to publish an Open Recorder release from this repository.## Quick startPick the script that matches the release type:```bashpnpm release:patchpnpm release:minorpnpm release:major```If the user wants to choose interactively, use:```bashpnpm release:dispatch```## PreconditionsBefore running a release command:1. Make sure the repo is on the branch the user wants to release from.2. Make sure `gh auth status` succeeds.3. If this release needs signed macOS artifacts and secrets are not configured yet, run:```bashpnpm release:setup-macos-signing```## Release type guidance- `patch`: bug fixes, small polish, or safe maintenance updates.- `minor`: new backward-compatible features.- `major`: breaking changes or compatibility resets.## Useful command patternsYou can pass extra flags through pnpm with `--`:```bashpnpm release:patch -- --notes "Bug fixes and stability improvements"pnpm release:minor -- --name "Open Recorder v1.4.0" --yespnpm release:major -- --latest false```Supported flags come from `scripts/dispatch-release-build.mjs`:- `--notes VALUE`- `--name VALUE`- `--latest true|false`- `--yes`- `--ref VALUE`- `--repo OWNER/REPO`## What the skill should do1. Confirm the intended release type if the user did not already specify patch, minor, or major.2. Check the preconditions above.3. Run the matching root package script.4. Report that the release PR workflow was dispatched and explain that GitHub Actions will calculate the next version and open or update the release PR.5. If the user asks how the release process works or something fails, read `references/release-process.md`.## Important behaviors- The local dispatcher does not update version files or create commits in the user's checkout.- It dispatches `.github/workflows/release-pr.yml`, and that workflow computes the next version and opens or updates the release PR.- Merging the release PR triggers `.github/workflows/release.yml`, which builds and publishes the actual GitHub release.

Frequently asked questions