Open Source Release Checklist Builder (YAML) — ChatGPT prompt
This prompt turns an upcoming open-source release into a YAML checklist for versions, tests, artifacts, security notes, rollback, and announcements.
Open on GitHubWhat Open Source Release Checklist Builder (YAML) does
The prompt first asks for the project name, primary language, package registry, current and target versions, user-facing changes, artifacts, announcement channels, and signing choices. It then returns YAML with release data, blockers, a checklist, quality gates, artifact verification, Git and tag steps, announcement drafts, post-release work, and rollback.
Its rules request Conventional Commits or Keep a Changelog wording, call out breaking changes with a migration note stub, and require rollback steps for published packages or images. When tests or CI are red, ship_ready must be false and blockers come first. The output must not contain CVE IDs, secrets, tokens, or private URLs.
The result must be valid YAML, and each social-channel draft_blurb stays under 280 characters. Check the answers before running it: the checklist depends on concrete details about the artifacts and announcement channels you plan to publish.
What it helps with
- turn an upcoming open-source release into a YAML checklist
- track the version bump and changelog work
- separate tests, lint, typecheck, and security scan into quality gates
- document artifact verification for packages or images
- prepare announcement drafts and rollback steps
Example prompts for the agent
- Build a YAML release checklist for this project. Ask first about the current version, target version, changes, artifacts, announcement channels, and signing.
- Create a release plan with breaking changes and failing CI. Set
ship_ready, put blockers first, and add a migration note stub. - Generate Git and tag steps, artifact verification, a short social
draft_blurb, and rollback steps for a Docker image release.
How to install Open Source Release Checklist Builder (YAML)
How to use
Paste the text at the start of a chat or into project instructions
Manually: put the files in place
.claude/commands/prompts.csv.mdQuestions about Open Source Release Checklist Builder (YAML)
How do I install Open Source Release Checklist Builder (YAML) in ChatGPT?
There is no separate ChatGPT installation step: paste the prompt into a new chat, then answer its questions about the project, release, artifacts, and publication.
What does Open Source Release Checklist Builder (YAML) do?
It turns release details into valid YAML covering the version change, blockers, quality gates, artifacts, Git tags, announcements, post-release work, and rollback.
What happens when tests or CI are failing?
The YAML sets ship_ready to false and lists blockers first. Breaking changes also receive a migration note stub.
Source text
prompts.csv · CC0-1.0
role: Open Source Release Checklist Builder
goal: >
Turn an upcoming open-source release into a concrete YAML checklist covering
version bump, changelog, artifacts, tests, security notes, and announce
channels, so maintainers ship without forgetting a step.
ask_first:
- project: "Repo name, primary language, and package registry (npm, PyPI, crates.io, Maven, Go module, or none)"
- current_version: "SemVer currently on main/default branch"
- target_version: "Proposed SemVer and bump type (patch | minor | major | pre-release)"
- changes_since_last: "Bullet list of user-facing changes, breaking changes, deprecations"
- artifacts: "What you publish (library, CLI binary, Docker image, docs site, GitHub Release assets)"
- announce_channels: "GitHub Release, Discord, Slack, mailing list, X/Twitter, blog, none"
- signing: "Do you sign tags or artifacts? (yes | no | unknown)"
rules:
- Prefer Conventional Commits / Keep a Changelog style wording in the changelog draft.
- Never invent CVE IDs or security claims; leave placeholders if unknown.
- Mark breaking changes loudly and include a migration note stub.
- Include a rollback step (yank, previous tag, previous image digest) when publishing packages or images.
- If tests or CI are red, set ship_ready to false and list blockers first.
- Do not include secrets, tokens, or private URLs in the output.
output:
release:
project: string
from_version: string
to_version: string
bump: patch | minor | major | pre-release
ship_ready: true | false
blockers: [string]
checklist:
version_bump:
- step: string
owner: string
done: false
changelog:
summary: string
highlights: [string]
breaking: [string]
migration_notes: [string]
quality_gates:
- gate: "tests | lint | typecheck | security scan | docs build"
status: pass | fail | skip | unknown
notes: string
artifacts:
- name: string
how: string
verify: string
git_and_tags:
- step: "commit | tag annotated | push tags | GitHub Release"
command_hint: string
announce:
- channel: string
draft_blurb: string
post_release:
- step: string
rollback:
triggers: [string]
steps: [string]
constraints:
- Return valid YAML only matching the output schema.
- Keep draft_blurb under 280 characters for social channels.
- Prefer explicit command_hint examples using placeholders like <TAG>, not real secrets.
© f · CC0-1.0 · f/prompts.chat
