pre-publish-review
Nuclear-grade 16-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (5 agents) for holistic review, and 1 oracle for overall release synthesis. Use before EVERY npm publish. Triggers: 'pre-publish review', 'review before publish', 'release review', 'pre-release review', 'ready to publish?', 'can I publish?', 'pre-publish', 'safe to publish', 'publishing review', 'pre-publish check'.
Best for npm package maintainersWorks with GitHubLow risk
⌘source
- author
@code-yeongyu- language
- TypeScript
★53kstars
4.2kforks
Apr 18, 2026
✦overview.md
Key Features
- ·Three-layer review with 16 specialized agents
- ·Deep analysis per logical change group
- ·Holistic review across the full changeset
- ·Final synthesis for overall release readiness
- ·Triggers automatically before npm publish
- ·Requires initial unpublished changes detection
Use Cases
- →Reviewing all changes before publishing a new npm package version
- →Ensuring code quality, security, and goal compliance for a release
- →Detecting breaking changes and deployment risks prior to publishing
- →Automating a comprehensive pre-publish checklist for CI/CD pipelines
Best for
- ✓npm package maintainers
- ✓release engineering teams
- ✓CI/CD pipelines with automated publishing
Not ideal for
- !Non-npm package publishing
- !One-off script execution without a release process
FAQs
name
pre-publish-review
description
Nuclear-grade 16-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (5 agents) for holistic review, and 1 oracle for overall release synthesis. Use before EVERY npm publish. Triggers: 'pre-publish review', 'review before publish', 'release review', 'pre-release review', 'ready to publish?', 'can I publish?', 'pre-publish', 'safe to publish', 'publishing review', 'pre-publish check'.
Pre-Publish Review — 16-Agent Release Gate
Three-layer review before publishing to npm. Every layer covers a different angle — together they catch what no single reviewer could.
| Layer | Agents | Type | What They Check |
|---|---|---|---|
| Per-Change Deep Dive | up to 10 | ultrabrain | Each logical change group individually — correctness, edge cases, pattern adherence |
| Holistic Review | 5 | review-work | Goal compliance, QA execution, code quality, security, context mining across full changeset |
| Release Synthesis | 1 | oracle | Overall release readiness, version bump, breaking changes, deployment risk |
Phase 0: Detect Unpublished Changes
Run /get-unpublished-changes FIRST. This is the single source of truth for what changed.
skill(name="get-unpublished-changes")
This command automatically:
- Detects published npm version vs local version
- Lists all commits since last release
- Reads actual diffs (not just commit messages) to describe REAL changes
- Groups changes by type (feat/fix/refactor/docs) with scope
- Identifies breaking changes
- Recommends version bump (patch/minor/major)
$install
1-click copynpx skills add code-yeongyu/oh-my-openagent --skill pre-publish-reviewSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
5/ 5
excellentVery clear and well structured, with almost no room for misunderstanding.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
5/ 5
very highHighly actionable with clear, concrete steps that an agent can follow directly.