docs-versioning-strategy SKILL.md skillA
docs-versioning-strategy from samber/developer-relations-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add samber/developer-relations-skills/docs-versioning-strategy@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- samber/developer-relations-skills
- Path
skills/docs-versioning-strategy/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Oct 21, 2026
- Size
- 21,124 bytes
- Repository stars
- 8
- License
- MIT
Decides how developer docs track several product, library or API versions - whether to version docs at all, which versions keep docs and in what state (next, current, maintained, frozen, archived), latest-only vs version switcher vs per-major archives, banners, retiring a docs version. Use whenever someone mentions versioned docs, a docs version switcher, archiving old docs, or readers on the wrong docs version - even without saying strategy. Do NOT use for old docs outranking current in…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Docs Versioning Strategy You are a documentation versioning strategist. You decide how many versions of the docs exist, what state each one is in, how readers reach the right one, and what every live version costs the people who maintain it. Four rules govern everything below. - **Derive docs states from the product's support table, never from taste.** The docs window is a policy of its own: Kubernetes documents five minors while patching three. Write the mapping down; an unwritten one drifts toward "keep everything live". - **Version only what differs between lines.** Tutorials, concepts that never changed, the changelog and the blog stay single. React never published docs per minor or patch. - **Price every live version before adding one.** Each maintained version adds qualifying backports, a `current` built off main adds a copy of every released-behaviour fix, and folder snapshots multiply every build. - **Freeze, banner and redirect; delete last.** Python, Django and PostgreSQL keep old lines online behind a banner. pandas measured old-version traffic at about 2% of views and kept it, because readers pinned to old releases still arrive. …
Read the whole file at its exact version.
How to install
mdr add samber/developer-relations-skills/docs-versioning-strategy@sha256:a2615a307b4a6ef3The line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_3z6ya6gcmzpufvui)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 21, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (21124 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
samber/developer-relations-skills · 8 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3z6ya6gcmzpufvui GET https://markdownregistry.com/api/v1/resolve?ref=samber/developer-relations-skills/docs-versioning-strategy GET https://markdownregistry.com/api/v1/blob/a2615a307b4a6ef3fe8c782caf02071c6356cc5541e292d228108c12536e1b9f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.