pre-publish-review — Claude Code skill: what it does, how to install
Orchestrates a 12-agent release gate for npm packages. Detects unpublished diffs and reviews breaking changes before you push to the registry.
npx skills add code-yeongyu/oh-my-openagent --skill pre-publish-review -a claude-codeWhat pre-publish-review does
The skill starts by running /get-unpublished-changes. It compares the active npm release against local commits in git, grouping diffs by functional area.
Review execution happens across three layers. First, up to 10 background ultrabrain agents inspect separate diff groups for edge cases and type errors. An orchestrator QA step and a gate reviewer then inspect overall code quality. Finally, a single oracle agent evaluates semver version bumps and release risks.
This workflow activates strictly when you ask for a pre-release review. Standard commands like /publish bypass this pipeline to ship immediately.
What it helps with
- catch subtle regressions and missing type guards across unreleased commits
- verify semver bump requirements across core packages and adapters
- inspect breaking changes in public interfaces and hook contracts
- split large git diffs into isolated scopes for parallel agent review
Example prompts for the agent
- Run a pre-publish review for the latest npm changes
- Ready to publish? Check our unreleased commits
- Can I publish this build to npm?
How to install pre-publish-review
1Skills CLI (Vercel)
npx skills add code-yeongyu/oh-my-openagent --skill pre-publish-review -a claude-code2Manually: put the files in place
~/.claude/skills/pre-publish-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pre-publish-review/
1Skills CLI (Vercel)
npx skills add code-yeongyu/oh-my-openagent --skill pre-publish-review -a codex2Manually: put the files in place
.agents/skills/pre-publish-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add code-yeongyu/oh-my-openagent --skill pre-publish-review -a cursor2Manually: put the files in place
.cursor/skills/pre-publish-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install code-yeongyu/oh-my-openagent pre-publish-review2Manually: put the files in place
.github/skills/pre-publish-review/SKILL.md1Skills CLI (Vercel)
npx skills add code-yeongyu/oh-my-openagent --skill pre-publish-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/code-yeongyu/oh-my-openagent --path .opencode/skills/pre-publish-reviewManually: put the files in place
.devin/skills/pre-publish-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add code-yeongyu/oh-my-openagent --skill pre-publish-review -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set4
The whole set →Similar
Questions about pre-publish-review
How to install pre-publish-review in Claude Code?
Run npx skills add code-yeongyu/oh-my-openagent --skill pre-publish-review -a claude-code. The skill will register directly in your environment.
What does pre-publish-review do?
It coordinates up to 12 agents across three layers to evaluate npm release readiness. Agents run parallel deep-dives on isolated diffs, followed by holistic QA and final version synthesis.
Does pre-publish-review trigger automatically during standard publish commands?
No, it activates only when you explicitly request a pre-release check. A direct /publish call deliberately skips the agent gate and ships right away.
