@nickcrew/release-prep
AUse when preparing a production release or release candidate - provides a checklist-driven workflow for validation, versioning, build optimization, documentation updates, and deployment readiness.
Install
agr install @nickcrew/release-prep --target claudeWrites 1 file into .claude/skills/, pinned to git-d2ca481b.
- .claude/skills/release-prep/SKILL.md
Document
name: release-prep description: Use when preparing a production release or release candidate - provides a checklist-driven workflow for validation, versioning, build optimization, documentation updates, and deployment readiness. keywords:
- changelog
- deploy prep
- prepare release
- release candidate
- release checklist
- release prep
- version bump file_patterns:
- '**/.github/workflows/release.yml'
- '**/CHANGELOG*'
- '**/RELEASE*'
- '/announcement/'
- '/changelog/'
- '/community/'
- '/release/'
- '/releases/' confidence: 0.86
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
- 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
Trustgrade A
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- passLicense
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-d2ca481b2e4d2026-07-31