pre-publish-review

Identify unpublished changes and produce a release-readiness verdict with a version bump recommendation.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/1thirteeng3/greenmoire --skill pre-publish-review-1thirteeng3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-publish-review
Source: https://github.com/1thirteeng3/greenmoire/tree/main/integrations/oh-my-openagent/.opencode/skills/pre-publish-review
Command: npx skills add https://github.com/1thirteeng3/greenmoire --skill pre-publish-review-1thirteeng3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Nuclear-grade pre-publish release gating using a three-layer, multi-agent review process to ensure npm publishes are safe, compliant, and well-scoped before release.

Core Features & Use Cases

  • Three-layer pre-publish review: per-change ultrabrain analysis (up to 10 agents), holistic review-work (5 agents), and a single release-synthesis oracle.
  • Phase-driven workflow: detect unpublished changes, group them, spawn agents in parallel, and synthesize a final readiness verdict.
  • Safe release governance: provides a final version bump recommendation and a consolidated set of findings to guide release decisions.

Quick Start

Trigger the pre-publish-review workflow on the current changes to gate an npm publish.

Frequently Asked Questions about pre-publish-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review npm unpublished changes before a release?

Reviewing unpublished npm changes requires identifying all commits since the last release, grouping them, and applying per-change analysis to generate a release-readiness verdict. This multi-agent workflow automates that exact process.

What is a multi-agent pre-publish review gate for npm packages?

A pre-publish review gate is a multi-layered analysis process that evaluates unpublished changes before an npm release. It uses per-change ultrabrain analysis, holistic review-work, and release synthesis to deliver a final readiness verdict.

How do I determine the correct version bump for my npm release?

Determining a version bump for an npm release involves synthesizing findings from per-change and holistic reviews of unpublished changes. The workflow provides a recommended version bump alongside its release-readiness verdict.

Can I use AI agents to automate release-readiness checks for npm publishes?

AI agents can automate release-readiness checks by spawning in parallel to analyze grouped unpublished changes. The workflow uses up to 10 agents for per-change analysis and 5 for holistic review, culminating in a single synthesis oracle.

What is the best way to ensure npm publishes are safe and well-scoped?

Ensuring npm publishes are safe and well-scoped requires a three-layer review process across unpublished changes. This approach applies per-change analysis, holistic review-work, and release synthesis to gate the publish decision.

Does this pre-publish review workflow require any dependencies?

The pre-publish review workflow operates without external dependencies, using a phase-driven process to detect unpublished changes, group them, and spawn parallel agents for analysis before delivering a readiness verdict.