version-control SKILL.md skillA
version-control from bislink360/styled-markdown is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add bislink360/styled-markdown/version-control@git:20261001.dca8800Pins git:20261001.dca8800 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- bislink360/styled-markdown
- Path
.claude/skills/version-control/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261001.dca8800, committed Oct 1, 2026
- First version recorded
- Sep 28, 2026
- Size
- 8,119 bytes
- Repository stars
- 3
- License
- MIT
Plan and run a release train in the Styled Markdown repository. Given a list of features for a release (e.g. "1.2.0: link completion, smd fmt, mermaid diagnostics"), create the release branch and one independent branch per feature, develop each in its own worktree, merge feature PRs into the release branch, then — after the release is tagged and published — merge the release branch into main. Use this skill whenever the user gives features for a version, asks to start/plan a release or…
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
# Version control: the release train
Every change reaches `main` through a release branch:
```text
main ──► release/vX.Y.Z ──► feat/a ──┐
├──► feat/b ──┼──(squash PRs)──► release/vX.Y.Z ──► tag vX.Y.Z ──► publish ──(merge commit PR)──► main
└──► fix/c ───┘
```
- `main` only ever contains **released** code, so it always matches the latest tag.
- `release/vX.Y.Z` is the integration branch for one version. It is opened at its version: the bump and changelog heading are its first commit.
- Each **major feature** gets its own branch from the release branch, so features are developed, reviewed and dropped independently.
The compatibility gate, versioning rules, changelog format and publishing steps come from the **smd-release** skill. Follow it at the points marked ▶ smd-release.
## 1. Plan the release from the feature list
1. Pin down the version and the feature list.
- If the user points at the roadmap ("the v1.2 items"), read that milestone with the styled-markdown-reader skill (`smd agent ROADMAP.smd --section "v1.2…"`) and take the unchecked items.
…Read the whole file at its exact version.
How to install
mdr add bislink360/styled-markdown/version-control@sha256:be8715bcb04468adThe line at the top of this page pins the label git:20261001.dca8800, 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_yx4zm7baf6y4lywy)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Sep 28, 2026 and Oct 1, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261001.dca8800 latest | 2026-10-01 | dca8800 | 8,119 B | A | view · diff |
| git:20260929.1fabbec | 2026-09-29 | 1fabbec | 8,017 B | A | view · diff |
| git:20260928.4106eef | 2026-09-28 | 4106eef | 7,796 B | A | view |
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 (8119 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
bislink360/styled-markdown · 3 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yx4zm7baf6y4lywy GET https://markdownregistry.com/api/v1/resolve?ref=bislink360/styled-markdown/version-control GET https://markdownregistry.com/api/v1/blob/be8715bcb04468ad92cf3221ee45572f7851f67ba021a9e7c6fb60673c3ce735
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.
More from bislink360/styled-markdown
Every file in bislink360/styled-markdown