release

Automate version bumps, tests, tags, npm publishing, and GitHub releases.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/shaun0927/codex-superskills --skill release-shaun0927
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/shaun0927/codex-superskills/tree/main/skills/release
Command: npx skills add https://github.com/shaun0927/codex-superskills --skill release-shaun0927

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end release process for codex-superskills, reducing manual steps and human error in versioning, packaging, and publishing.

Core Features & Use Cases

  • Version bump propagation across package.json, installer code, tests, and README.
  • Run test suite, create and push Git tags, publish to npm, and generate a GitHub release.
  • Use cases include standard patch/minor/major releases and hotfix releases.

Quick Start

Invoke the release workflow with the target version to automatically bump, test, tag, publish, and 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 publishing and git tag creation for version releases?

You can automate npm publishing and git tag creation by running a scripted release workflow that updates version references, runs tests, commits changes, creates git tags, pushes to origin, and publishes to npm. This eliminates manual steps and human error in versioning.

What is an end-to-end release workflow for version bumps?

An end-to-end release workflow automates version bump propagation across package.json, installer code, tests, and README. It sequentially runs your test suite, creates and pushes Git tags, publishes to npm, and generates a GitHub release with built-in safety checks and rollback points.

Can I use an automated release workflow for hotfix deployments?

Yes, you can use an automated release workflow for hotfix releases. The workflow applies the same version bumping, testing, git tagging, npm publishing, and GitHub release generation sequence used for standard patch, minor, and major releases to ensure hotfix consistency.

How do I propagate version numbers across package.json, tests, and README?

To propagate version numbers across package.json, tests, and README, use an automated release script that updates version references throughout your project. This ensures all files reflect the target version before committing changes and creating git tags for the release.

What safety checks are included when automating software versioning and publishing?

Automated software versioning and publishing workflows include safety checks and rollback points throughout the scripted sequence. These checks run before committing changes, creating git tags, pushing to origin, and publishing to npm to prevent failed or inconsistent releases.