GitHub Swarm Code Review
ruvnet/agentic-flow
Reviews GitHub pull requests with a swarm of specialized agents covering security, performance, architecture, style and accessibility, driven by the gh CLI and ruv-swarm.
Runs a multi-agent review before an npm release, with per-change analysis, a holistic review and a final readiness verdict, and only when you ask for it.
Install Pre-Publish Release Review
$ npx skills add code-yeongyu/oh-my-openagent --skill pre-publish-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install code-yeongyu/oh-my-openagent pre-publish-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pre-publish-review .claude/skills/pre-publish-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pre-publish-review" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/pre-publish-review into .claude/skills/pre-publish-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-publish-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/pre-publish-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add code-yeongyu/oh-my-openagent --skill pre-publish-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install code-yeongyu/oh-my-openagent pre-publish-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/pre-publish-review .agents/skills/pre-publish-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pre-publish-review" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/pre-publish-review into .agents/skills/pre-publish-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-publish-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add code-yeongyu/oh-my-openagent --skill pre-publish-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install code-yeongyu/oh-my-openagent pre-publish-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/pre-publish-review .cursor/skills/pre-publish-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pre-publish-review" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/pre-publish-review into .cursor/skills/pre-publish-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-publish-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/code-yeongyu/oh-my-openagent.git --path .agents/skills/pre-publish-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add code-yeongyu/oh-my-openagent --skill pre-publish-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install code-yeongyu/oh-my-openagent pre-publish-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/pre-publish-review .gemini/skills/pre-publish-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pre-publish-review" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/pre-publish-review into .gemini/skills/pre-publish-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-publish-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install code-yeongyu/oh-my-openagent pre-publish-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add code-yeongyu/oh-my-openagent --skill pre-publish-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/pre-publish-review .github/skills/pre-publish-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pre-publish-review" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/pre-publish-review into .github/skills/pre-publish-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-publish-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add code-yeongyu/oh-my-openagent --skill pre-publish-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install code-yeongyu/oh-my-openagent pre-publish-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/pre-publish-review .opencode/skills/pre-publish-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pre-publish-review" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/.agents/skills/pre-publish-review into .opencode/skills/pre-publish-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-publish-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pre-publish-review- GitHub stars
- 70k
- Token cost
- ~4.3k tokens
- SKILL.md length
- 734 words
- Files
- 1
- Skills in repo
- 45
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Runs a multi-agent review before an npm release, with per-change analysis, a holistic review and a final readiness verdict, and only when you ask for it.
- Works in 5 steps: Detect Unpublished Changes → Parse Changes into Groups → Spawn All Agents → …
- Checking whether a package is safe to publish to npm
- SKILL.md covers Release Layer Taxonomy, Phase 0: Detect Unpublished…, Phase 1: Parse Changes into… and Phase 2: Spawn All Agents, plus 3 more sections
- Calls git, npm and node
What it does
The release gate has three layers. It begins by running the get-unpublished-changes skill, which compares the published npm version with the local one, lists commits since the last release, reads the real diffs, groups changes by type, flags breaking changes and recommends a version bump. Up to ten agents then each examine one logical group of changes for correctness, edge cases and adherence to existing patterns.
A second layer runs the review-work skill, in which an orchestrator does manual QA and one reviewer checks goal compliance, code quality, security and missed context across the whole change set. A single oracle agent then writes the release synthesis covering readiness, version bump, breaking changes and deployment risk, with findings mapped onto three release layers of the project.
It is written around one project's package layout and runs only when you explicitly ask for a pre-publish review. An ordinary publish or release request does not trigger it, because a separate command ships directly.
When your agent uses it
- Checking whether a package is safe to publish to npm
- Reviewing everything changed since the last npm release before shipping
- Deciding the version bump and spotting breaking changes ahead of a release
Example prompts
- “Do a pre-publish review of everything since the last npm release.”
- “I want to know if this release is safe to publish, so check it before I ship.”
- “Review the unpublished changes and tell me which version bump they need.”
Requirements
- An npm package with a published version to compare against
- The get-unpublished-changes and review-work skills
- An agent setup that can spawn parallel review agents
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Detect Unpublished Changes
- Parse Changes into Groups
- Spawn All Agents
- Collect Results
- Final Verdict
What it can do on your machine
Read from SKILL.md and the folder at commit ae4ddd2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitnpmnode
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Pre-Publish Release Review loads about 4.3k tokens when it runs. Until then it costs about 175 tokens; SKILL.md has 734 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 734 words (~4,296 tokens).
“Three-agent-layer review before publishing to npm. Every layer covers a different angle, and every result is mapped onto the release layers below.”
- name
- pre-publish-review
Files
Just SKILL.md in .agents/skills/pre-publish-review of code-yeongyu/oh-my-openagent.
Open the folder on GitHubat commit ae4ddd2
Compare with similar skills
Pre-Publish Release Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pre-Publish Release Review this skillcode-yeongyu/oh-my-openagent | 70k | — | ~4.3k | Automated safety check: Pass | Custom licence | |
| GitHub Swarm Code Reviewruvnet/agentic-flow | 819 | 6 repos | ~6.5k | Automated safety check: Pass | None | |
| Solo ReviewLeoYeAI/openclaw-master-skills | 2.2k | — | ~5.6k | Automated safety check: Notes | MIT | |
| Release-Green Validationdiegosouzapw/OmniRoute | 74k | — | ~740 | Automated safety check: Pass | MIT | |
| CI Triageandymai/brepjs | 115 | — | ~3.7k | Automated safety check: Pass | Apache-2.0 | |
| Open Code Review CLIalibaba/open-code-review | 45k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Solo Review
LeoYeAI/openclaw-master-skills
Final code review and quality gate — run tests, check coverage, audit security, verify acceptance criteria from spec, and generate ship-ready report.
Release-Green Validation
diegosouzapw/OmniRoute
Runs or reads a local Release-Green observer for an exact base or PR candidate and separates hard failures, advisory drift and incomplete evidence.
CI Triage
andymai/brepjs
This skill should be used when a brepjs GitHub Actions job is red or behaving oddly on github.com (a remote CI run, not a local pre-commit/pre-push hook) — "CI failed", "ci-pass is failing", "npm ci…
Open Code Review CLI
alibaba/open-code-review
Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.
O2 Review Loop
openobserve/openobserve
Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.
More from code-yeongyu/oh-my-openagent
All 45 skills in this repoast-grep Structural Search
code-yeongyu/oh-my-openagent
Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.
Browser Control with Omowright
code-yeongyu/oh-my-openagent
Drives a real browser through the omowright library, either the user's own signed-in browser or a separate browser the code launches, for forms, QA, screenshots and scraping.
Codex Plugin QA
code-yeongyu/oh-my-openagent
Tests the omo Codex plugin in an isolated CODEX_HOME with a local mock model, proving hooks fired through app-server notifications without touching ~/.codex.
Coding Agent Session Finder
code-yeongyu/oh-my-openagent
Finds, reads and reconstructs past coding-agent sessions across Codex, Claude, OpenCode, Senpi and many other local agent logs.
LSP Setup
code-yeongyu/oh-my-openagent
Detects which languages a project uses, installs the matching language server, writes its config and checks it with a real call so diagnostics and go-to-definition work.
OpenCode QA Toolkit
code-yeongyu/oh-my-openagent
Tests the opencode coding agent itself: its CLI, server, plugin hooks and events, the terminal UI under tmux, and its SQLite session database, using tested helper scripts.
Related
Works with
Categories
Questions about Pre-Publish Release Review
What does Pre-Publish Release Review do?
Runs a multi-agent review before an npm release, with per-change analysis, a holistic review and a final readiness verdict, and only when you ask for it. The release gate has three layers. It begins by running the get-unpublished-changes skill, which compares the published npm version with the local one, lists commits since the last release, reads the real diffs, groups changes by type, flags breaking changes and recommends a version bump.
When should I use Pre-Publish Release Review?
Pre-Publish Release Review fits situations like: checking whether a package is safe to publish to npm; reviewing everything changed since the last npm release before shipping; deciding the version bump and spotting breaking changes ahead of a release.
How do I install Pre-Publish Release Review in Claude Code?
Run `npx skills add code-yeongyu/oh-my-openagent --skill pre-publish-review -a claude-code`. Or copy the skill folder (.agents/skills/pre-publish-review in code-yeongyu/oh-my-openagent) into .claude/skills/pre-publish-review in your project. Claude Code loads it when a task matches its description.
How do I install Pre-Publish Release Review in Codex?
Run `npx skills add code-yeongyu/oh-my-openagent --skill pre-publish-review -a codex`. Or copy the skill folder (.agents/skills/pre-publish-review in code-yeongyu/oh-my-openagent) into .agents/skills/pre-publish-review in your project. Codex loads it when a task matches its description.
Can I use Pre-Publish Release Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add code-yeongyu/oh-my-openagent --skill pre-publish-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pre-publish-review, .gemini/skills/pre-publish-review, .github/skills/pre-publish-review and .opencode/skills/pre-publish-review in your project.
What does Pre-Publish Release Review need to run?
Going by SKILL.md and its folder, Pre-Publish Release Review needs the command-line tools its instructions call (git, npm and node). Our summary lists: An npm package with a published version to compare against; The get-unpublished-changes and review-work skills; An agent setup that can spawn parallel review agents.
Does Pre-Publish Release Review access the network?
SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Pre-Publish Release Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Pre-Publish Release Review use?
Pre-Publish Release Review has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Pre-Publish Release Review use?
About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Pre-Publish Release Review?
Skills that share tags, products or a category with Pre-Publish Release Review: GitHub Swarm Code Review (ruvnet/agentic-flow, 819 stars), Solo Review (LeoYeAI/openclaw-master-skills, 2.2k stars), Release-Green Validation (diegosouzapw/OmniRoute, 74k stars) and CI Triage (andymai/brepjs, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pre-Publish Release Review?
code-yeongyu (a GitHub user) maintains it in code-yeongyu/oh-my-openagent, which has 69,917 GitHub stars. The repository holds 45 skills in this directory. The repository was last updated on October 9, 2026.
Source: code-yeongyu/oh-my-openagent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.