pre-publish-review

# 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) **Save the full output** — it feeds directly into Phase 1 grouping and all agent prompts. Then capture raw data needed by agent prompts: ```bash # Extract versions (already in /get-unpublished-changes output) PUBLISHED=$(npm view oh-my-opencode version 2>/dev/null || echo "not published") LOCAL=$(node -p "require('./package.json').vers...