release-prep

Run linting, tests, builds, and release checks for Toolbox libraries.

48|4|Updated Dec 22, 2025

Search Tags:#documentation #build #release #test #lint #pre-release

Ready to run

npx skills add https://github.com/OysteinAmundsen/toolbox --skill release-prep-oysteinamundsen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-prep
Source: https://github.com/OysteinAmundsen/toolbox/tree/main/.github/skills/release-prep
Command: npx skills add https://github.com/OysteinAmundsen/toolbox --skill release-prep-oysteinamundsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prepare and automate all pre-release checks to ensure Toolbox libraries are linted, tested, built, and documented before release.

Core Features & Use Cases

Lint all projects to enforce code quality across the toolbox libraries
Run tests and builds for all libraries to guarantee integration compatibility
Check bundle size budgets, review CHANGELOGs, and validate documentation updates
Use Case: When preparing a new library release, run the full checklist to catch issues before publishing

Quick Start

Invoke the release-prep skill with the target library name to run the full pre-release checklist.

Frequently Asked Questions about release-prep

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

FAQPage Schema

How do I automate pre-release checks for linting, testing, and building libraries?▼

To automate pre-release checks, you can run a scripted workflow that enforces linting, tests, and builds across all libraries. This ensures code quality and integration compatibility before publishing a release.

What is included in a pre-release readiness workflow for publishing?▼

A pre-release readiness workflow includes running linting, tests, and builds, while also enforcing bundle-size budgets, reviewing CHANGELOGs, and validating documentation updates to gate failures before publishing.

How do I enforce bundle size budgets and changelog reviews before publishing?▼

You can enforce bundle size budgets and changelog reviews by running an automated pre-release checklist. This deterministic process validates documentation updates and strictly gates failures to align with Conventional Commits practices.

Can I validate documentation updates and docs site builds before a library release?▼

Yes, you can validate documentation updates and docs site builds before a library release. The automated process reviews documentation changes and verifies site validation as part of the strict pre-publishing readiness gate.

What is the best way to ensure Conventional Commits alignment in release pipelines?▼

The best way to ensure Conventional Commits alignment is to implement an auditable, scripted pre-release process. This enforces bundle-size budgets, changelog reviews, and test gates to strictly align with standard release practices.

Does the pre-release checklist gate failures to prevent publishing broken builds?▼

Yes, the pre-release checklist implements strict gating of failures to prevent publishing broken builds. It deterministically halts the release pipeline if linting, tests, builds, or documentation validation fail.