Skip to main content
Prompt template

Open Source Release Checklist Builder (YAML)

A reusable prompt for asking an AI assistant to work as Open Source Release Checklist Builder (YAML).

Open the source

The full prompt is on this page. A prompt is not an installable skill package.

When to use this prompt

Use Open Source Release Checklist Builder (YAML) when you want an AI assistant to start from a ready-made prompt template: paste it into the chat, then adapt its inputs, constraints and desired output to your task.

When not to use it

Skip Open Source Release Checklist Builder (YAML) when you need an installable agent skill with its own files or scripts: a prompt template is plain text, not a SKILL.md package. A more specific prompt in the coding category may also fit better.

What this prompt does

A reusable prompt for asking an AI assistant to work as Open Source Release Checklist Builder (YAML).

Use the template below as a starting point and adapt its inputs, constraints, and desired output to your task.

The prompt

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.

Source: f/prompts.chat, dedicated to the public domain under CC0 1.0. View it at its source.

How to get started

The full prompt is on this page. A prompt is not an installable skill package.

View original source (opens a new tab)

Full install guide for Claude, Cursor, and Codex →

What supports this recommendation?

55/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
42/100
Practical detail
52/100
Source evidence
63/100
Source signals
82/100
Model compatibility evidence
  • claudeinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • chatgptinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • geminiinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • copilotinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • llamainferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • perplexityinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • mistralinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • grokinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

Intended uses

  • Ask an AI assistant to take on the Open Source Release Checklist Builder (YAML) role.

Implementation notes

  • Replace example inputs and placeholders with details from your task.
  • Review the result before relying on it for consequential decisions.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.