skills.rest
VledicFranco
VledicFrancoCOMMUNITY
Explore all skills by this author →
Website𝕏@francoaramburoGitHub

release-publish

Automate npm release publishing with QA, versioning, changelog, git tagging, and GitHub Releases.

Updated Feb 8, 2026
Search Tags:#automation#git#versioning#npm#github#release#ci
One-click install
npx skills add https://github.com/VledicFranco/organon --skill release-publish-vledicfranco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-publish
Source: https://github.com/VledicFranco/organon/tree/main/.claude/skills/release-publish
Command: npx skills add https://github.com/VledicFranco/organon --skill release-publish-vledicfranco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publish new versions to npm with proper QA, version bumping, changelog updates, git tagging, and GitHub Release automation.

Core Features & Use Cases

  • End-to-end release workflow from QA to publication, ensuring version consistency and provenance for Organon tooling.
  • Automated version bump decisions (patch/minor/major), changelog maintenance, and multi-package updates.
  • GitHub Release creation and CI trigger to publish artifacts to npm after checks pass.

Quick Start

Run node scripts/release.mjs <patch|minor|major> after QA completes to publish the new release.

Frequently Asked Questions about release-publish

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

FAQPage Schema
How do I automate npm release publishing with git tagging and changelog updates?▼

Automating npm release publishing requires a workflow that enforces pre-publish QA, determines the appropriate version bump, updates changelogs, applies git tags, and creates a GitHub Release to trigger CI publication.

What is the process for bumping versions across multiple npm packages before a release?▼

Bumping versions across multiple npm packages involves determining the correct semantic version increment (patch, minor, or major) and applying automated file updates across all affected packages to ensure version consistency before publication.

How do I trigger CI to publish npm artifacts after creating a GitHub Release?▼

Triggering CI to publish npm artifacts is done by creating a GitHub Release after QA and version bumping, which automatically initiates the continuous integration pipeline to push the new package version to npm.

Can I use automated release workflows for npm projects using Organon tooling?▼

Automated release workflows are designed specifically for npm projects using Organon tooling, ensuring consistent release processes across patch, minor, and major updates with integrated QA and CI triggers.

What's the best way to enforce pre-publish QA before an npm version bump?▼

Enforcing pre-publish QA before an npm version bump requires integrating quality assurance checks directly into the release workflow, ensuring no version increment or changelog update occurs until all validation passes.

Why does my automated npm release workflow need to create a GitHub Release?▼

Creating a GitHub Release in an automated npm release workflow establishes provenance and serves as the trigger event for CI pipelines to safely publish the versioned artifacts to the npm registry.

Related Skills

Explore More Software Engineering Skills→
TMI-appsTMI-apps
2

push

Validate and push committed Git changes to a remote repository.

Official
Intermediate
klaudworksklaudworks
181

npm-publisher

Automate npm package releases with version bumps, Git tags, and CI/CD publishing.

Community
Intermediate
heltondoriaheltondoria
1

release

Automate semantic versioning, changelog generation, and Git tagging for releases.

Community
Advanced
luanrodriguesluanrodrigues
2

bee:dev-devops

Generate and update Dockerfiles, docker-compose.yml, and .env.example files.

Community
Advanced