skills.rest
carrotwaxr
carrotwaxrCOMMUNITY
Explore all skills by this author →
GitHub

pre-release

Run pre-release validation of CI, builds, tests, linters, and Docker images.

37|6|Updated Oct 10, 2025
Search Tags:#testing#build#docker#lint#pre-release#ci#integration-tests
One-click install
npx skills add https://github.com/carrotwaxr/peek-stash-browser --skill pre-release-carrotwaxr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pre-release
Source: https://github.com/carrotwaxr/peek-stash-browser/tree/main/.claude/skills/pre-release
Command: npx skills add https://github.com/carrotwaxr/peek-stash-browser --skill pre-release-carrotwaxr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents regressions and failed releases by providing a deterministic, repeatable checklist that validates CI health, build outputs, tests, linters, and container builds before creating a release tag.

Core Features & Use Cases

  • CI Verification: Confirms main branch CI is green before any local work proceeds.
  • Build Integrity: Rebuilds shared types/artifacts to catch missing build steps that only appear on clean checkouts.
  • Comprehensive Checks: Runs server and client unit tests, linters, type checks, integration tests, client production build, and Docker image build to ensure release readiness.
  • Use Case: Use this checklist as the gatekeeping routine prior to tagging a production release to reduce hotfixes and rollback risk.

Quick Start

Run the pre-release checklist by verifying main's CI is passing, rebuilding shared artifacts, executing server and client tests and linters, running integration tests, performing the client production build, and building the Docker image.

Frequently Asked Questions about pre-release

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

FAQPage Schema
How do I verify CI status and build integrity before creating a release tag?▼

To verify release readiness, you must confirm the main branch CI is green, rebuild shared types to catch missing build steps, and execute comprehensive checks across server and client workspaces before tagging.

What steps are needed for a pre-release validation sequence in a monorepo with shared types?▼

A pre-release validation sequence requires rebuilding shared artifacts, running server and client unit tests, executing linters and type checks, performing integration tests, and completing a client production build.

Does this pre-release checklist work with Docker builds and separate server and client workspaces?▼

Yes, the pre-release checklist is designed for codebases with separate server and client workspaces, shared types, integration tests, and containerized production images, including reproducible Docker image creation.

Why should I run a pre-release validation routine before tagging a production release?▼

Running a pre-release validation routine prevents regressions and failed releases by providing a deterministic checklist that validates CI health, build outputs, tests, and container builds before tagging, reducing hotfixes and rollback risk.

What's the best way to ensure Docker image creation is reproducible during release preparation?▼

The best way to ensure reproducible Docker image creation during release preparation is to include the Docker image build as the final step of a comprehensive pre-release checklist after all tests and lint checks pass.

What happens if I skip rebuilding shared types and artifacts before running pre-release checks?▼

Skipping the rebuild of shared types and artifacts risks missing build steps that only appear on clean checkouts, which can cause failed releases and regressions that the pre-release validation sequence is designed to catch.

Related Skills

Explore More Software Engineering Skills→
vanducngvanducng
5

ship

Automate feature branch landing into main or beta with testing and PR creation.

Community
Advanced
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

production-deployment-phase

Promote validated staging builds to production with semantic versioning and health checks.

Community
Advanced
josuenavarroaguadojosuenavarroaguado

ci-cd-and-automation

Automate GitHub Actions CI/CD pipelines with quality gates and preview deployments.

Community
Advanced
barefootfordbarefootford
584

release

Automate ButterCut releases with version bumps, changelog, git tags, gem build, and GitHub release.

Community
Advanced