postkit-release

Bump the version, create a GitHub Release, and publish postkit to npm.

4|Updated Apr 16, 2026

Search Tags:#changelog #versioning #github #release #npm publish #git tagging #CI workflow

Ready to run

npx skills add https://github.com/Trystan-SA/postkit --skill postkit-release

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: postkit-release
Source: https://github.com/Trystan-SA/postkit/tree/main/.claude/skills/postkit-release
Command: npx skills add https://github.com/Trystan-SA/postkit --skill postkit-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you reliably ship a new postkit version by coordinating version bumping, tagging, GitHub Release creation, and npm publishing without breaking the release order.

Core Features & Use Cases

Preflight guardrails: Ensures the repo is clean, on the main branch, up to date with origin/main, and that both gh and npm credentials are authenticated before changing anything.
Controlled semver bump: Prompts you to choose patch, minor, or major and updates the version using npm version to ensure the tag is created correctly.
Release communication: Builds a commit-based changelog since the previous tag, asks for confirmation, then creates a GitHub Release so watchers are notified and finally publishes the package to npm.

Quick Start

Use the postkit-release skill in the postkit repository and tell it you want to ship a release.

Frequently Asked Questions about postkit-release

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

FAQPage Schema

How do I publish an npm package and create a GitHub release with a changelog at the same time?▼

To publish an npm package with a GitHub release, you bump the version, push the commit and tag to GitHub, create a release with a commit-based changelog, then publish to npm. This enforces the correct release order to prevent broken deployments.

What's the best way to automate npm version bumping and git tagging for a release?▼

Automating npm version bumping and git tagging uses the `npm version` command to update the version, commit the change, and create the tag. This ensures the git tag matches the package version before pushing to GitHub.

Do I need a clean working tree before cutting a new npm release?▼

Yes, you need a clean working tree before cutting a release. Preflight guardrails enforce a clean repository on the main branch, synced with origin/main, and verify both gh and npm credentials are authenticated before making changes.

How are GitHub release changelogs generated from commit history?▼

GitHub release changelogs are generated by collecting commit history since the previous tag. The release process builds this commit-based changelog, asks for confirmation, and creates the GitHub Release to notify project watchers.

Can I cut a release if my npm package scope does not match the repository?▼

No, you cannot cut a release if the scope is incorrect. The release process requires the correct repository scope by checking the package.json name and verifies success at each step to ensure safe npm publishing.

Why does my npm publish workflow fail after creating a git tag?▼

An npm publish workflow may fail after creating a git tag if the release order is broken. Coordinating version bumping, tagging, GitHub Release creation, and npm publishing in the required sequence verifies success at each step to avoid failures.