release-package

Create and publish new npm package versions with changelog updates.

Updated Oct 11, 2025
One-click install
npx skills add https://github.com/tnez/docent --skill release-package
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-package
Source: https://github.com/tnez/docent/tree/main/.docent/skills/docent/release-package
Command: npx skills add https://github.com/tnez/docent --skill release-package

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git cli, gh cli, npm, Node.js, awk.

What problem does it solve?

Manual package releases are prone to errors, inconsistent versioning, and forgotten documentation updates. This Skill provides a comprehensive, automated workflow for creating and publishing new npm package versions, ensuring semantic versioning, accurate changelogs, and seamless deployment via GitHub Actions.

Core Features & Use Cases

  • Pre-Release Health Check: Validates code quality, tests, and documentation before release.
  • Automated Versioning & Changelog: Guides on determining version bumps and updating CHANGELOG.md with structured release notes.
  • GitHub Actions Integration: Triggers automated npm publishing and GitHub Release creation upon pushing a tagged commit.
  • Post-Release Verification: Confirms package availability on npm and proper GitHub Release creation.
  • Use Case: You're ready to release a new version of your npm package. Use this Skill to guide you through pre-release checks, automatically bump the version, update the changelog, and then push a tagged commit that triggers a fully automated, verified release to npm and GitHub.

Quick Start

Release a new patch version of this npm package.

Frequently Asked Questions about release-package

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

FAQPage Schema
How do I automate npm package releases with version bumping and changelog updates?

Automate npm package releases by using this Skill to validate code, bump semantic versions, update CHANGELOG.md, push tagged commits, and trigger GitHub Actions to publish to npm. It handles versioning, changelog generation, and verification end to end.

What checks does an automated release workflow perform before publishing to npm?

Pre-release health checks validate code quality, run tests, and verify documentation before release. The workflow ensures all prerequisites pass before bumping the version and pushing the tagged commit that triggers npm publishing.

Can I use GitHub Actions to automatically publish npm packages when I push a git tag?

Yes. Push a tagged commit to trigger GitHub Actions to automatically publish your npm package. This Skill guides you through creating the tag, configuring npm publish access in GitHub secrets, and monitoring CI/CD until npm completes the release.

Do I need write access to the repository and npm publishing permissions to release a package?

Yes. You need git write access to create and push tags to main, ability to create GitHub releases, npm publish access, and npm credentials configured in GitHub secrets. This Skill requires Node.js >= 18, git cli, gh cli, and npm installed.

How do I verify that my npm package published successfully after an automated release?

Post-release verification confirms the package is available on npm registry and the GitHub Release was created correctly. This Skill monitors CI/CD completion and validates both npm and GitHub artifacts after publishing.

What's the best way to keep CHANGELOG.md synchronized with npm package versions?

Automate changelog updates as part of your release workflow. This Skill guides updating CHANGELOG.md with structured release notes alongside version bumps, ensuring documentation stays consistent with semantic versioning before pushing tagged commits.