Run any Skill in Manus with one click

automate-npm-release

Stars161

Forks4

UpdatedJuly 6, 2026 at 16:06

Automate npm package publishing via GitHub Actions for single-package repos and independent monorepo packages, including bumpp version tags, GitHub release notes, trusted publishing, provenance, and package-scoped release tags. Use when setting up or modifying npm publish workflows, npm release pipelines, version bumping, package-scoped monorepo releases, changelogithub release notes, trusted publishing, provenance badges, NPM_TOKEN, or OIDC publishing.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

jd-solanki

jd-solanki/slidev-theme-dracula

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

5 files

SKILL.md

readonly

name	automate-npm-release
description	Automate npm package publishing via GitHub Actions for single-package repos and independent monorepo packages, including bumpp version tags, GitHub release notes, trusted publishing, provenance, and package-scoped release tags. Use when setting up or modifying npm publish workflows, npm release pipelines, version bumping, package-scoped monorepo releases, changelogithub release notes, trusted publishing, provenance badges, NPM_TOKEN, or OIDC publishing.
disable-model-invocation	true

Automate npm Release

Use this skill to set up npm release automation. First identify the repository shape, then load the matching reference:

Single publishable package: see SINGLE_PACKAGE.md.
Workspace monorepo with independently published packages: see MONOREPO.md.

Shared rules

npm requires the first publish to be done manually for each public package:

npm publish --access public

Prefer npm trusted publishing/OIDC when the project asks for it. Configure the package on npmjs.com after the first manual publish, then use id-token: write in GitHub Actions. Ensure package.json has repository.url exactly matching the GitHub repo URL (case-sensitive) — required for provenance validation.
If using token-based publishing, configure actions/setup-node with registry-url: https://registry.npmjs.org so NODE_AUTH_TOKEN can authenticate npm publish.
In pnpm workspaces, publish via pnpm pack followed by npm publish <tarball> --access public. This lets pnpm rewrite workspace:* dependencies while npm handles trusted publishing/OIDC. Use changelogithub only for GitHub release notes/releases.
Always run checks, tests, and package builds before publishing.
Keep the private workspace root unpublished; publish from the actual package directory.

Quick choice

Use single-package release automation when one package.json owns the npm artifact and one v* tag maps to one package.

Use monorepo release automation when multiple workspace packages publish independently. In that flow, tags must encode the package, such as cli-v0.1.0, and GitHub release-note generation must use explicit previous same-package tag ranges.

Workflow examples

EXAMPLE_WORKFLOW.yml — single-package token/provenance workflow.
MONOREPO_WORKFLOW.yml — package-scoped monorepo workflow using trusted publishing and changelogithub.

More from this repository

same repository

automate-commit-based-gh-release-changelog

jd-solanki/slidev-theme-dracula

Automate GitHub release creation and changelog generation from Conventional Commits using changelogithub — includes GitHub release mechanics, tag-based triggers, required permissions, and fetch-depth gotcha. Use when setting up GitHub releases, generating changelogs from commits, using changelogithub, or configuring v* tag triggers and contents:write permissions.

2026-07-06161

clean-code

jd-solanki/slidev-theme-dracula

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", "readable code", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing pull requests for readability, refactoring messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.

2026-07-06161

code-organisation

jd-solanki/slidev-theme-dracula

Decide where code lives — the directory tree, module and package boundaries, and the layout inside a file. Use when starting a new project or directory tree, placing a new file/class/function, grouping code into modules or packages, splitting an oversized file or module, naming directories/packages/files, separating source from generated build artifacts, or auditing an existing codebase's structure.

2026-07-06161

coding

jd-solanki/slidev-theme-dracula

Composition skill which invokes sub-skills for coding tasks. It is a meta-skill that orchestrates the use of other coding-related skills.

2026-07-06161

comment-code

jd-solanki/slidev-theme-dracula

Write clear, useful in-code comments and documentation that capture what the code cannot say for itself. Use this skill whenever writing or revising comments, docstrings, interface/API documentation, function or class headers, or inline explanations — and whenever reviewing code for comment quality or being asked to "document," "add comments," "explain in comments," or improve existing comments. Apply it even when the request only mentions writing the code, since fresh code is the moment to document it well.

2026-07-06161

coding

jd-solanki/slidev-theme-dracula

Composition skill which invokes sub-skills for coding tasks. It is a meta-skill that orchestrates the use of other coding-related skills.

2026-07-06161

name	automate-npm-release
description	Automate npm package publishing via GitHub Actions for single-package repos and independent monorepo packages, including bumpp version tags, GitHub release notes, trusted publishing, provenance, and package-scoped release tags. Use when setting up or modifying npm publish workflows, npm release pipelines, version bumping, package-scoped monorepo releases, changelogithub release notes, trusted publishing, provenance badges, NPM_TOKEN, or OIDC publishing.
disable-model-invocation	true

Automate npm Release

Use this skill to set up npm release automation. First identify the repository shape, then load the matching reference:

Single publishable package: see SINGLE_PACKAGE.md.
Workspace monorepo with independently published packages: see MONOREPO.md.

Shared rules

npm requires the first publish to be done manually for each public package:

npm publish --access public

Prefer npm trusted publishing/OIDC when the project asks for it. Configure the package on npmjs.com after the first manual publish, then use id-token: write in GitHub Actions. Ensure package.json has repository.url exactly matching the GitHub repo URL (case-sensitive) — required for provenance validation.
If using token-based publishing, configure actions/setup-node with registry-url: https://registry.npmjs.org so NODE_AUTH_TOKEN can authenticate npm publish.
In pnpm workspaces, publish via pnpm pack followed by npm publish <tarball> --access public. This lets pnpm rewrite workspace:* dependencies while npm handles trusted publishing/OIDC. Use changelogithub only for GitHub release notes/releases.
Always run checks, tests, and package builds before publishing.
Keep the private workspace root unpublished; publish from the actual package directory.

Quick choice

Use single-package release automation when one package.json owns the npm artifact and one v* tag maps to one package.

Workflow examples

EXAMPLE_WORKFLOW.yml — single-package token/provenance workflow.
MONOREPO_WORKFLOW.yml — package-scoped monorepo workflow using trusted publishing and changelogithub.