release

Automate lockstep releases of the tx workspace across GitHub and npm.

6|3|Updated Jan 28, 2026

Search Tags:#automation #git #workflow #versioning #npm #release #preflight

Ready to run

npx skills add https://github.com/jamesaphoenix/tx --skill release-jamesaphoenix

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing a new lockstep version of tx to GitHub and npm with preflight validation, workflow monitoring, and registry verification to ensure a clean, auditable release process.

Core Features & Use Cases

Preflight validation and enforced local checks prior to publish
Lockstep version bumps across all workspace files
Automated GitHub release creation, tag handling, and npm verification
Continuous monitoring of publish workflows with guardrails and rollback paths
Conventional-commit driven release process across packages

Quick Start

Provide a target version argument to initiate the full release workflow and monitor preflight, publish, and verification steps.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate lockstep version bumps across an npm workspace?▼

The release workflow automates lockstep npm workspace versioning by updating the version field across all workspace files before running preflight checks and publishing to the registry.

What is a preflight validation check in a continuous delivery workflow?▼

Preflight validation in a release workflow runs local automated checks and scripts prior to npm publish to catch errors early. It acts as a guardrail to ensure only validated code is tagged and shipped to GitHub and npm.

How do I coordinate multi-package GitHub releases and npm tags?▼

Multi-package releases are coordinated by providing a target version argument to the release workflow, which creates the GitHub release, pushes the corresponding tags, and verifies the published npm package versions.

Can I use conventional commits to drive a multi-package npm release?▼

Yes, the release workflow supports a conventional-commit driven release process across packages, using commit history to validate and coordinate version bumps and GitHub release creation.

How do I monitor npm publish workflows with rollback paths?▼

The release workflow provides continuous monitoring of publish workflows with built-in guardrails and rollback paths, tracking the publish process from preflight through registry verification.

Do I need a specific Git or npm environment to run automated release workflows?▼

You need a GitHub and npm environment configured for workspace packages, as the release workflow pushes tags to GitHub and verifies package versions against the npm registry.