About release-prep
A release-preparation skill for teams coordinating release candidates or production deployments. It organizes validation, version and documentation updates, artifact builds, and deployment and rollback planning into a checklist-driven workflow.
Key features
- 01Confirm release scope and version
- 02Run tests and security checks
- 03Update versions, changelog, and docs
- 04Build and validate production artifacts
- 05Prepare deployment and rollback plans
Use cases
- 01Prepare a release candidate
- 02Coordinate pre-release validation
- 03Standardize version and changelog updates
- 04Plan a production rollout and rollback
MCP support
This is an agent skill, not an MCP server or client. The input does not describe MCP integration.
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ nickcrew/ claude-cortex --skill release-prepAfter installing, type/release-prepin Claude Code to confirm it loaded.
Bundled filesreferences/prepare-release.md
Details
From the project READMERelease 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
| Task | Load reference |
|---|---|
| Release preparation | skills/release-prep/references/prepare-release.md |
Workflow
- Confirm release scope and version.
- Load the release preparation reference.
- Run pre-release validation (tests, security, performance).
- Update versions, changelog, and docs.
- Build production artifacts and validate.
- 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
Comments
Markdown supported