publish (Release Manager)
Give it a bump type and it drives the whole release: trigger the GitHub Actions publish workflow, draft release notes, announce on Discord, and verify npm.
AutomationAdvanced★ 67,531⑂ 5,507AI score 6/10Last updated: Aug 9, 2026
What it does
publish turns Claude into a release manager that refuses to stop halfway through a ship.
- Required argument:
patch/minor/major— if missing, it stops and asks immediately - Pre-flight checks: uncommitted change detection, remote sync via
git pull --rebase && git push - Workflow trigger:
gh workflow run publish -f bump=<type>, then captures the run ID - Active polling: 30-second job-level polling (never idle sleeps) with stage reporting: test → prepare-release-state → publish-platform → publish-main
- Better release notes: writes a user-impact "headline layer" and prepends it above the auto-generated changelog under a zero-content-loss policy
- Completion contract: the turn may only end when all five are green — run success, release exists, summary applied, Discord announced, npm version verified
- Platform spot-checks: samples darwin-arm64 / linux-x64 / windows-x64 binary packages
It also enforces a strict "ship-only" rule: no code re-review, no fix-and-re-audit loops during a publish.
Who it's for
- Maintainers publishing npm packages via GitHub Actions who hand-write release notes and announcements every time
- Anyone burned by an agent that triggered a release workflow and then ended its turn with nothing verified
- Teams that want a documented, repeatable release runbook
- Not a fit if you have no CI/CD pipeline or only run
npm publishmanually
Examples
- Patch release: "publish patch" → the skill registers a todo list, triggers the workflow, drafts the bug-fix summary while CI runs, prepends it to the release, posts to Discord, and confirms the version with
npm view. - Minor feature release: "release minor" → commits are grouped into themes (e.g. "⚡ 3x Faster Rule Parsing") and written as a product announcement instead of a git log dump.
- Failure handling: if the run fails, it prints
gh run view --log-failed, reports the failing target, and STOPS rather than patching the tree mid-publish.
Caution: the file hard-codes real repo names plus Discord channel and bot IDs — replace them with your own before use.
· · · Install guide · · ·
Install in the Claude app (no terminal)
- Download the ZIP with the button below.
- In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
- Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
Install in Claude Code
Let Claude do it — paste this into Claude Code
Install the skill I found on Claude Skill Mart. Copy the .agents/skills/publish folder from the GitHub repo code-yeongyu/oh-my-openagent into my ~/.claude/skills/publish/. When it's done, tell me in one line what this skill can do.
Install with a command instead
git clone https://github.com/code-yeongyu/oh-my-openagent.git /tmp/oh-my-openagent && mkdir -p ~/.claude/skills/publish && cp /tmp/oh-my-openagent/.agents/skills/publish/SKILL.md ~/.claude/skills/publish/SKILL.md⚠ This is a third-party skill. Check the source repository before installing.
- Open a terminal and move to a working directory.
- Clone the repository:
git clone https://github.com/code-yeongyu/oh-my-openagent.git - Create the skill folder:
mkdir -p ~/.claude/skills/publish - Copy the file:
cp oh-my-openagent/.agents/skills/publish/SKILL.md ~/.claude/skills/publish/SKILL.md - Edit
SKILL.mdand replace the package names, repo paths, Discord channel/bot IDs, and workflow name with your own. - Prepare prerequisites:
gh auth loginfor the GitHub CLI, npm publish rights, and a GitHub Actions workflow namedpublish. - Restart Claude Code and invoke it with a bump type, e.g.
publish patch. - Test against a scratch repository first so a misconfigured run never ships a real version.
View source on GitHub ↗License: NOASSERTION