release

Automate npm release workflows with version bumps, builds, and GitHub releases.

2|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/seasonedcc/coerce-form-data --skill release-seasonedcc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/seasonedcc/coerce-form-data/tree/main/.claude/skills/release
Command: npx skills add https://github.com/seasonedcc/coerce-form-data --skill release-seasonedcc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release automation for the coerce-form-data npm package to ensure consistent versioning, building, publishing, and GitHub releases with minimal manual steps.

Core Features & Use Cases

  • Automates version bumping and changelog notes
  • Builds and publishes to npm and creates a GitHub release
  • Validates checks, pushes tags, and coordinates follow-up tasks

Quick Start

Trigger the release workflow when you are ready to publish a new version and let it bump the version, build, publish, and create the GitHub release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate npm publish and GitHub release workflows end-to-end?

You can automate npm publish and GitHub release workflows by bumping versions, running build and test checks, pushing commits and tags, publishing to npm, and creating a GitHub release with changelog notes in one continuous process.

What's the best way to bump package versions and update lockfiles for a release?

Bumping package versions and updating lockfiles can be automated by reading the current version from package.json, applying patch, minor, or major updates, and pushing the updated tags and lockfiles directly to your repository.

How does an automated release workflow handle lint, tsc, and test validation?

An automated release workflow validates your code by running lint, tsc, build, and test checks sequentially before proceeding to push commits, prompt for npm publish, and create the GitHub release.

Can I generate changelog notes automatically when creating a GitHub release?

Yes, generating changelog notes is integrated into the release workflow, automatically compiling changes and attaching them when creating the GitHub release after the npm package is published.

Do I need to manually confirm before publishing to npm during the release process?

No, the release workflow prompts you for npm publish confirmation before pushing to the registry, ensuring a safe and repeatable release process across patch, minor, and major updates.

What are the limitations of automating npm releases across different version bumps?

Automating npm releases applies to project maintenance scenarios requiring repeatable, safe processes across patch, minor, and major updates, but relies on standard package.json structures and GitHub for tag and release management.