Skip to content
Back to skills

Prepare Release

ASecurity

Use when preparing a release candidate, release notes, artifact promotion, deployment readiness check, migration notes, or rollback plan. Defaults to read-only readiness analysis and never publishes or deploys without explicit confirmation.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 17, 2026
ai-agentsgitsecurity

Security analysis

A100/100

Scanned October 17, 2026

npx -y skills add ByronScottJones/Agents --skill prepare-release --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Prepare Release?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Prepare Release
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/byronscottjones-prepare-release/badge)](https://www.skillsdirectory.com/skills/byronscottjones-prepare-release)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: prepare-release
user-invocable: false
description: "Use when preparing a release candidate, release notes, artifact promotion, deployment readiness check, migration notes, or rollback plan. Defaults to read-only readiness analysis and never publishes or deploys without explicit confirmation."
---

# Prepare Release

Coordinate `release.md`, Git history, CI results, artifacts, and deployment risk.

## Parameters

- `owner`, `repository`, `pullRequest`: optional release source.
- `version`: required or inferred from project convention.
- `environment`: target promotion environment; default `staging`.
- `mode`: `notes`, `readiness`, `candidate`, `promote`, or `rollback-plan`; default `readiness`.
- `requireChecks`: default `true`.
- `format`: `summary`, `json`, or Markdown release notes; default `summary`.

## Workflow

1. Inspect commits, merged changes, version configuration, migrations, and CI status.
2. Generate notes covering behavior changes, risks, migrations, dependencies, and rollback.
3. Verify artifact identity, provenance, tests, security scans, and environment gates.
4. Identify backward-compatibility and data-migration sequencing risks.
5. For candidate or promotion modes, require explicit confirmation and verify the
   exact artifact being promoted.
6. Record deployment evidence and post-release verification requirements.

## Safety

- Do not publish tags, releases, or deployments without explicit authorization.
- Never promote an artifact that has not passed required checks.
- Redact secrets and sensitive plan or test output.

## Output

Return version, source revision, artifact identity, readiness checks, release
notes, migration requirements, rollback plan, blockers, and next steps.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.