semantic-versioning SKILL.md skillA
semantic-versioning from tuliosousapro/saas-blueprint is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tuliosousapro/saas-blueprint/semantic-versioning@git:20260520.5565189Pins git:20260520.5565189 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tuliosousapro/saas-blueprint
- Path
skills/semantic-versioning/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260520.5565189, committed May 20, 2026
- Size
- 1,838 bytes
- Repository stars
- 5
- License
- MIT
Manages project versioning following Semantic Versioning (SemVer) principles. Calculates increments based on changes and synchronizes version across documentation and metadata. Use when the user asks to "bump the version", "prepare a release", or when the `changelog` skill calls for a release.
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
# Semantic Versioning Skill ## Instructions ### 1. Detect Current Version - Read the latest version from `CHANGELOG.md` (e.g., the most recent header `## [X.Y.Z]`). - Read the version from `.github/repository-metadata.json`. - If they differ, flag the mismatch to the user and ask which is authoritative. ### 2. Analyze Changes Scan the changes since the last release: - If using `changelog` skill: Look at the items under `[Unreleased]` or the new version block being prepared. - If using `git log`: Scan for Conventional Commits types. ### 3. Determine Increment Type Follow these priority rules: 1. **MAJOR** (X.0.0): Any "BREAKING CHANGE" footer or `!` after the type (e.g., `feat!:`). 2. **MINOR** (x.Y.0): Any `feat` commit or "Added" entry in the changelog. 3. **PATCH** (x.y.Z): Any `fix`, `perf`, `refactor` commit or "Fixed"/"Changed" entry in the changelog. 4. **No Change**: If only `docs`, `chore`, `style`, `test`, `build`, or `ci` changes are found, default to PATCH unless the user specifies otherwise. ### 4. Apply Version Update Update the following files in a single pass: …
Read the whole file at its exact version.
How to install
mdr add tuliosousapro/saas-blueprint/semantic-versioning@sha256:45da7f3f3528343bThe line at the top of this page pins the label git:20260520.5565189, 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_pefmapoi6qsj7hcm)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 20, 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 (1838 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
tuliosousapro/saas-blueprint · 5 stars · license MIT · pushed 2026-08-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pefmapoi6qsj7hcm GET https://markdownregistry.com/api/v1/resolve?ref=tuliosousapro/saas-blueprint/semantic-versioning GET https://markdownregistry.com/api/v1/blob/45da7f3f3528343b65e55ec241c6188a4809b31665bb39de083cd8e7122c746d
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 tuliosousapro/saas-blueprint
Every file in tuliosousapro/saas-blueprint