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.
Best use case
release-prep is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when preparing a production release or release candidate - provides a checklist-driven workflow for validation, versioning, build optimization, documentation updates, and deployment readiness.
Teams using release-prep should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/release-prep/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How release-prep Compares
| Feature / Agent | release-prep | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when preparing a production release or release candidate - provides a checklist-driven workflow for validation, versioning, build optimization, documentation updates, and deployment readiness.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 | Task | Load reference | | --- | --- | | Release preparation | `skills/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