Every premium and members-only resource for $9.99/month, as a no-commitment subscription. See the plans

PalateKit

Sign in
Menu

Request a resource

Describe the resource you are missing in one sentence. We will email you when it is published.

0 / 280

A page, a video or an image online.

Unlock PalateKit

Unlock everything

Plan

Paying means accepting our terms of sale.

Secure payment by Stripe. Receipts and invoices sent by email.

Welcome back

Sign in to install, download or save this resource. A free account is enough for free resources.

Open source release policy v1.0.0

Use this resource to write the release policy of an open source project

New

  • 331 downloads
  • 140 likes
  • 130 saves

Free

Install with the CLI

In a terminal, from the folder you want:

npx --yes palatekit@latest install release-policy-versioning

With no option, the skill goes to ~/.agents/skills/; add --agent claude-code (or codex, cursor…) to target an agent.

First time: connect the CLI with

npx --yes palatekit@latest login

The agent chooses the numbering scheme (SemVer, 0.x, CalVer and others), defines what counts as breaking for this project, then sets pre-release channels, cadence, supported versions and deprecation. You get a RELEASES.md file ready for review.

Mostly picked by

Updated November 2, 2026

Card for the “Open source release policy” skill

Details

Works in
Install guides
Generates with
Your agent's model
Licence
MIT

Similar resources

View all

What you get

  • SKILL.md: eight-step method, from mapping readers to publishing
  • references/release-policy-template.md: RELEASES.md policy template
  • references/versioning-schemes.md: comparison of numbering schemes

Good fit for

  • You are torn between SemVer and CalVer and want to settle it in writing
  • Your users complain about breaking changes in minor releases

Not for

    Tags

    • versioning
    • semver
    • release
    • maintainer

    About

    You say

    “Write the release policy for my library: it has been on 0.x for two years and companies run it in production.”

    Card for the “Open source release policy” skill

    Skill published by samber under the MIT license, delivered in its original version.

    Show more

    How to use it

    1. Install the skill in your agent's skills folder
    2. Ask your agent to write the release policy of an open source project
    3. Review and adjust the result

    Content preview

    Files

    • evals/evals.json41 KB
    • LICENSE1.1 KB
    • NOTICE-PALATEKIT.md0.5 KB
    • references/ecosystem-tooling.md4 KB
    • references/release-policy-template.md6.7 KB
    • references/scheme-switching.md3.3 KB
    • references/versioning-schemes.md8 KB
    • SKILL.md19.5 KB

    Origin and licence

    Listed unmodified

    Author
    samber
    Source
    github.com/samber/developer-relations-skills/tree/a12240a5a8a15a460ab17aa870df37f14814bf7d/skills/oss-release-policy
    Licence
    MIT

    Notice

    « oss-release-policy » (samber, MIT) livré dans sa version d'origine : fiche en français et en anglais par PalateKit.

    User reviews

    –

    No ratings yet

    Loading reviews…

    Delete your review?

    Your rating and comment will be removed from the page.