skills.rest
raphaelchristi
raphaelchristiCOMMUNITY
Explore all skills by this author →
GitHub

dev:release

Automate npm package releases with changelog generation and GitHub publishing.

43|5|Updated Mar 31, 2026
Search Tags:#automation#changelog#versioning#npm#github#release#tagging
One-click install
npx skills add https://github.com/raphaelchristi/harness-evolver --skill dev-release-raphaelchristi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev:release
Source: https://github.com/raphaelchristi/harness-evolver/tree/main/.claude/skills/dev-release
Command: npx skills add https://github.com/raphaelchristi/harness-evolver --skill dev-release-raphaelchristi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the manual, error-prone process of preparing and publishing a new release by validating the repository state, generating user-facing changelog entries, bumping versions, tagging commits, creating a GitHub release, and publishing to npm so maintainers can release reliably and consistently.

Core Features & Use Cases

  • Interactive bump selection: Prompted choice between patch, minor, or major bumps to compute the new semantic version.
  • Changelog generation: Aggregate and rewrite commit messages into a Keep a Changelog-style entry and present it for review before publishing.
  • Version synchronization: Update package.json and plugin metadata, commit changes, create an annotated git tag, and push tags to the remote.
  • Release orchestration: Create a GitHub release with notes and publish the package to npm, then verify the published version.
  • Use Case: Use this workflow when you are ready to cut a new release of harness-evolver to ensure changelog accuracy, consistent versioning, and successful npm publication.

Quick Start

Run dev:release and choose patch, minor, or major to validate the repo, generate and confirm the changelog entry, bump versions, tag and push the release, create the GitHub release, and publish to npm.

Frequently Asked Questions about dev:release

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

FAQPage Schema
How do I automate npm publish and GitHub release from the command line?▼

Automate npm publish and GitHub release by validating the repository state, generating changelog entries, bumping versions, tagging commits, creating a GitHub release, and publishing to npm. This workflow ensures consistent versioning and reliable publication through git and CLI tools.

How do I generate a changelog and bump a semantic version before publishing a package?▼

Generate a changelog and bump a semantic version by interactively choosing patch, minor, or major. The workflow aggregates commit messages into a Keep a Changelog-style entry for review, updates package.json, commits changes, and pushes a git tag to the remote.

Do I need GitHub CLI and npm credentials to automate Node.js package releases?▼

Yes, automating Node.js package releases requires git commit and push access, GitHub CLI authentication, npm publish credentials, and write access to package.json, CHANGELOG.md, and repository tags to successfully orchestrate tagging and publication.

What is the best way to keep a changelog and create an annotated git tag for a new release?▼

The best way to keep a changelog and create an annotated git tag is to aggregate commit messages into a structured entry, bump the version in package.json, commit the changes, create an annotated git tag, and push the tag to the remote repository for release.

Can I review the changelog entry before the version bump and npm publish happen?▼

Yes, you can review the changelog entry before publishing. The workflow generates a Keep a Changelog-style entry from commit messages and presents it for review before proceeding with the version bump, tagging, and npm publication.

Why does my npm publish workflow fail during GitHub release creation?▼

An npm publish workflow may fail during GitHub release creation if GitHub CLI authentication is missing, npm publish credentials are invalid, or write access to repository tags, package.json, and CHANGELOG.md is restricted. Validating repository state before release helps prevent these errors.

Related Skills

Explore More Software Engineering Skills→
tneztnez

release-package

Create and publish new npm package versions with changelog updates.

Community
Intermediate
different-aidifferent-ai
249

publish-cli

Publish the agent-bank CLI to npm and verify its version.

Official
Intermediate
Tonybleything76Tonybleything76

Changelog Generator

Generate changelog entries from Git commit history using Conventional Commits.

Community
Advanced
vanman2024vanman2024
3

Version Management

Apply semantic versioning, generate changelogs from commits, and create release tags.

Community
Basic