pre-publish-qa

Run pre-publish QA checks for npm packages with builds, tests, and health gates.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/VledicFranco/organon --skill pre-publish-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-publish-qa
Source: https://github.com/VledicFranco/organon/tree/main/.claude/skills/pre-publish-qa
Command: npx skills add https://github.com/VledicFranco/organon --skill pre-publish-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates comprehensive pre-publish QA checks to ensure npm packages meet quality gates before release, reducing release-risk.

Core Features & Use Cases

  • Automates build validation and test execution across multi-package repositories.
  • Verifies health gates, file lists, and changelog consistency to prevent misaligned releases.
  • Enforces version alignment and frontmatter integrity as part of the publish workflow.

Quick Start

Run the pre-publish QA workflow before npm publish to validate builds, tests, health, and version alignment.

Frequently Asked Questions about pre-publish-qa

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

FAQPage Schema
How do I run pre-publish QA checks for npm packages to prevent flawed releases?

Run pre-publish QA checks to validate builds, execute tests, verify repository health, and enforce version alignment before npm publish. This automated workflow ensures package quality gates are met to reduce release risk.

What is the best way to validate builds and tests in multi-package repositories before publishing?

Validating builds and tests in multi-package repositories requires automating build validation with npm-build and executing tests with npm-test. This ensures all packages meet quality gates before release.

How do I verify version alignment and changelog consistency before an npm publish?

Verify version alignment and changelog consistency by running repository health checks and frontmatter verification via organon verify. This prevents misaligned releases across multi-package repositories.

Does this pre-publish QA workflow support npm release workflows in multi-package repositories?

This pre-publish QA workflow fully supports multi-package repositories and npm release workflows. It validates builds, tests, health gates, and changelog integrity to ensure flawless releases.

Why do I need to run health gates and frontmatter verification before publishing npm packages?

Running health gates and frontmatter verification before publishing npm packages prevents misaligned releases and enforces version alignment. This automated validation reduces release risk by checking file lists and changelog consistency.

What npm pre-publish validation steps are required to ensure flawless releases?

Required npm pre-publish validation steps include running builds with npm-build, executing tests with npm-test, verifying repository health with organon health, and ensuring version alignment via organon verify.