Sign in
Explore
Prompts · PromptTesting & SecuritySecurity auditsUnit tests & TDDReviewed

Open Source Release Checklist Builder (YAML)

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 annou…

View on GitHub
Kind
Prompt
Works with
Any agent
Source
prompts.chat: prompts for developers @ dcab86ce9c26
Path
items/open-source-release-checklist-builder-yaml
Jobs
Review, Testing, Git workflow
Topics
Security audits, Unit tests & TDD
Tags
role-prompt

Credit

Made by
f
Original
https://prompts.chat/prompts?q=Open+Source+Release+Checklist+…
License
CC0-1.0

Listed by Skill Manifest; not made by us.

InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
Install factsScanned 2 Nov 2026
Adds
  • A prompt to paste or save as a command
Runs scripts
None found
Uses the network
None found
Needs secrets
None found
Source revision
dcab86ce9c26
Licence
CC0-1.0
Last activity
Unknown
Review
Reviewed

Found by a static scan of the stored text; nothing is run. “None found” is not a guarantee, so read what you install before you run it.

  • The source's last activity is not known yet
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.
…