prepare-release

Validate builds, tests, docs, and create changesets for releases.

21|4|Updated Feb 19, 2026

Search Tags:#automation #changelog #versioning #documentation #release #ci #changeset

Ready to run

npx skills add https://github.com/tylerjrbuell/reactive-agents-ts --skill prepare-release-tylerjrbuell

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prepare-release
Source: https://github.com/tylerjrbuell/reactive-agents-ts/tree/main/.agents/skills/prepare-release
Command: npx skills add https://github.com/tylerjrbuell/reactive-agents-ts --skill prepare-release-tylerjrbuell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The release process for Reactive Agents is error-prone and manually intensive. This Skill automates pre-release checks, ensures builds and tests complete successfully, audits documentation, and standardizes changelog creation to produce a reliable release package.

Core Features & Use Cases

Pre-flight validation: full build, test suite, and typecheck gates before releasing.
Documentation audit: verifies docs reflect code changes and package counts.
Changeset & changelog: generates a changeset and writes a consistent changelog entry for a new release version.
Release planning: coordinates across packages to plan version bumps and publish readiness.

Quick Start

Run the prepare-release workflow to validate the build, tests, and docs, generate a changeset, and update the changelog.

Frequently Asked Questions about prepare-release

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

FAQPage Schema

How do I automate changelog creation and build validation for a release?▼

Automating changelog creation and release validation ensures consistent versioning by running full build, test, and typecheck gates before generating a changeset. This verifies documentation reflects code changes and writes a standardized changelog entry for the new release version.

What is a changeset and when do I need it for versioning?▼

A changeset is a standardized record of code modifications needed during version cuts to coordinate package version bumps. You need it when planning a release to ensure CI passes, docs stay current, and changelog entries remain consistent across affected packages.

Do I need bun tooling to run pre-release checks and documentation audits?▼

Yes, bun tooling is required to execute the standard scripts for build, test, and typecheck validation. You also need repository access to verify documentation reflects code changes, audit package counts, and generate the changeset for publish readiness.

How do I ensure CI passes and docs stay current before a version cut?▼

To ensure CI passes during a version cut, run pre-flight validation that executes the full build, test suite, and typecheck gates. To keep docs current, perform a documentation audit verifying docs reflect code changes and package counts before generating the changelog.

What's the best way to standardize release workflows across multiple packages?▼

The best way to standardize release workflows is to automate release planning that coordinates version bumps across packages. This validates builds, generates consistent changesets, and ensures documentation audits pass before publishing, reducing manual errors during version cuts.

Why does my release workflow fail due to inconsistent changelog entries?▼

Release workflows fail due to inconsistent changelog entries when manual changeset creation omits standardized formatting. Automating changeset generation and changelog updates during the version cut ensures entries remain consistent and documentation audits pass.