skills.rest
gerald-ica
gerald-icaCOMMUNITY
Explore all skills by this author →
GitHub

pre-publish-review

Detect unpublished npm changes and organize them into review groups.

Updated Apr 14, 2026
Search Tags:#automation#npm#agents#code-review#diff-analysis#pre-publish#release-review
One-click install
npx skills add https://github.com/gerald-ica/opencode-config-snapshot --skill pre-publish-review-gerald-ica
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pre-publish-review
Source: https://github.com/gerald-ica/opencode-config-snapshot/tree/main/opencode/skills/omo-pre-publish-review
Command: npx skills add https://github.com/gerald-ica/opencode-config-snapshot --skill pre-publish-review-gerald-ica

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Nuclear-grade pre-publish gate ensuring deep, multi-agent review before npm release.

Core Features & Use Cases

  • Multi-layer review: Per-change ultrabrain analysis, holistic review, and final release synthesis.
  • Automated grouping: Groups unpublished changes into reviewable cohorts.
  • Release readiness: Determines readiness for publishing and guides version decision.

Quick Start

Run the pre-publish review workflow on the target package to validate unpublished changes before 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 automate code review for unpublished npm changes before a release?▼

Automated pre-publish review detects unpublished npm changes since the last release and stages them for structured analysis. It groups changes into cohorts for parallel review, applying multi-layer analysis to produce a final release-readiness assessment.

What is a multi-agent pre-publish gate and how does it work?▼

A multi-agent pre-publish gate enforces layered review before npm publishing. It applies per-change ultrabrain analysis, holistic review, and release synthesis to evaluate unpublished code changes and determine overall release readiness.

How do I group unpublished code changes for parallel diff analysis?▼

Group unpublished code changes for parallel diff analysis using automated grouping strategies. The review pipeline organizes changes into up to 10 structured groups, enabling concurrent analysis of each cohort before holistic synthesis.

Does automated release review determine npm version readiness?▼

Yes, automated release review determines npm version readiness by synthesizing per-change and holistic analysis results. The pipeline evaluates staged unpublished changes and guides the version decision based on the final release-readiness assessment.

Can I use multi-agent review for large unpublished diffs with many changes?▼

Multi-agent review handles large unpublished diffs by applying a structured grouping strategy. It organizes numerous changes into up to 10 groups for parallel analysis, ensuring thorough per-change and holistic review before release synthesis.

What are the limitations of automated pre-publish code review?▼

Automated pre-publish code review focuses strictly on unpublished npm changes since the last release. It requires a clear diff to stage for review, and the pipeline limits grouping to 10 cohorts for parallel analysis to manage review complexity.

Related Skills

Explore More Software Engineering Skills→
1thirteeng31thirteeng3

pre-publish-review

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

Community
Advanced
bmad-code-orgbmad-code-org
51.7k

bmad-os-release-module

Automates npm release process including changelog drafting, versioning, git tagging, publishing, and GitHub releases.

Official
Advanced
sommiosommio
1

ce:review

Orchestrate multi-agent code reviews and merge findings into a single report.

Community
Advanced
code-yeongyucode-yeongyu
67.6k

pre-publish-review

Orchestrate a 16-agent pre-publish release gate for npm packages.

Community
Advanced