release

Enforce pre-release checks before publishing npm packages via changesets.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/kjfsm/notion-headless-cms --skill release-kjfsm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/kjfsm/notion-headless-cms/tree/main/.claude/skills/release
Command: npx skills add https://github.com/kjfsm/notion-headless-cms --skill release-kjfsm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures safe, controlled npm releases by performing pre-release checks and disabling automatic model invocation. It provides explicit, manual release steps triggered only when /release is requested.

Core Features & Use Cases

  • Pre-release checks with changeset status, build, typecheck, and tests to ensure release readiness.
  • Explicit release workflow guidance including provenance checks and publishing steps.
  • Safe operation guidance, including disabling automatic model invocation to prevent unintended activations.

Quick Start

Run the release skill to perform pre-publish checks and prepare for npm publication.

Frequently Asked Questions about release

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

FAQPage Schema
How do I run pre-release checks before publishing to npm?

To run pre-release checks before publishing to npm, you can trigger an explicit release workflow that validates changeset status, executes builds, runs typechecks, and performs tests to ensure package readiness.

What is the safest way to publish npm packages in a CI/CD pipeline?

The safest way to publish npm packages in CI/CD pipelines involves disabling automated model invocation and requiring an explicit command cue to execute validated build, test, and provenance verification steps.

How do changesets integrate with npm publishing workflows?

Changesets integrate with npm publishing by providing a pre-release status check that validates pending changes, ensuring only reviewed and built package versions proceed to the final publication step.

Can I prevent automated npm releases during CI/CD validation?

Yes, you can prevent automated npm releases by disabling automatic model invocation and enforcing a manual release cue, ensuring pre-release checks only run when explicitly requested.

Does npm release verification require provenance checks?

Yes, npm release verification can include provenance checks as part of the explicit release workflow to validate the build integrity and secure the package publication process.

Why are my npm pre-release builds failing typecheck and tests?

Pre-release builds fail typecheck and tests when the release workflow enforces strict validation rules, halting the npm publication process until all codebase checks and build verifications pass successfully.