agentsclimarketplace

Release prep

Skill NickCrew/Claude-Cortex/skills/release-prep

Use when preparing a production release or release candidate - provides a checklist-driven workflow for validation, versioning, build optimization, documentation updates, and deployment readiness.From its SKILL.md

Install
npx -y skills add NickCrew/Claude-Cortex --skill release-prep

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.8 KB, 248 tokens by cl100k_base, as published. Nobody here has run it

Release Prep

Overview

Standardize release preparation with a safety-first checklist: validate quality and security, update versions and docs, build production artifacts, and prepare rollout/rollback plans.

When to Use

  • Preparing a release candidate or production deploy
  • Coordinating pre-release validation and documentation
  • Ensuring versioning, changelog, and build steps are consistent

Avoid when:

  • You only need a quick version bump or doc update
  • The release process is owned by a separate automation pipeline

Quick Reference

TaskLoad reference
Release preparationskills/release-prep/references/prepare-release.md

Workflow

  1. Confirm release scope and version.
  2. Load the release preparation reference.
  3. Run pre-release validation (tests, security, performance).
  4. Update versions, changelog, and docs.
  5. Build production artifacts and validate.
  6. Produce deployment checklist and rollback plan.

Output

  • Release readiness checklist
  • Validation results and blockers
  • Deployment plan with rollback steps

Common Mistakes

  • Skipping security or performance checks
  • Shipping without updating changelog or docs
  • Building artifacts without validating environment parity

What ships with it: 1 file

4.9 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most ship operate skills give in 248 tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07

  • Document a rollback plan before deploymentin 41 of 779, across 22 files
  • Update the changelogin 21 of 779, across 19 files
  • Run the test suitein 20 of 779
  • Create an annotated git tagin 20 of 779
  • Clean up feature flags after full rolloutin 18 of 779, across 10 files
  • Verify deployment health after launchin 18 of 779, across 10 files
  • Test both feature flag statesin 17 of 779, across 9 files
  • Verify the working tree is cleanin 17 of 779
  • Make database migrations backward-compatiblein 16 of 779, across 8 files
  • Set up error monitoring before launchin 15 of 779, across 7 files
  • Monitor metrics at each rollout stagein 14 of 779, across 5 files
  • Create a GitHub releasein 14 of 779

Said here and by no other author read

  • load the release preparation reference
  • produce deployment checklist and rollback plan

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,629. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.