apply-semantic-versioning SKILL.md skillA
apply-semantic-versioning from pjt222/agent-almanac is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pjt222/agent-almanac/apply-semantic-versioning@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pjt222/agent-almanac
- Path
i18n/caveman-lite/skills/apply-semantic-versioning/SKILL.md- Versions recorded
- 3
- Latest version
- v1.0, committed Aug 17, 2026
- First version recorded
- Apr 19, 2026
- Size
- 8,829 bytes
- Repository stars
- 43
- License
- MIT
Apply semantic versioning (SemVer 2.0.0) to determine the correct version bump based on change analysis. Covers major/minor/patch classification, pre-release identifiers, build metadata, and breaking change detection. Use when preparing a new release to determine the correct version number, after merging changes before tagging, evaluating whether a change constitutes a breaking change, adding pre-release identifiers, or resolving disagreement about what version bump is appropriate.
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
# Apply Semantic Versioning Determine and apply the correct semantic version bump by analyzing changes since the last release. This skill reads version files, classifies changes as breaking (major), feature (minor), or fix (patch), computes the new version number, and updates the appropriate files. Follows [SemVer 2.0.0](https://semver.org/) specification. ## When to Use - Preparing a new release and need to determine the correct version number - After merging a set of changes and before tagging a release - Evaluating whether a change constitutes a breaking change - Adding pre-release identifiers (alpha, beta, rc) to a version - Resolving disagreement about what version bump is appropriate ## Inputs - **Required**: Project root directory containing a version file (DESCRIPTION, package.json, Cargo.toml, pyproject.toml, or VERSION) - **Required**: Git history since the last release (tag or commit) - **Optional**: Commit convention in use (Conventional Commits, free-form) - **Optional**: Pre-release label to apply (alpha, beta, rc) - **Optional**: Previous version if not readable from files ## Procedure ### Step 1: Read Current Version …
Read the whole file at its exact version.
How to install
mdr add pjt222/agent-almanac/apply-semantic-versioning@sha256:96fd9884a79a25f2The line at the top of this page pins the label v1.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_4n77zpljtx7f4zpl)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Apr 19, 2026 and Aug 17, 2026, about one every 60 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0 latest | 2026-08-17 | a784899 | 8,829 B | A | view · diff |
| v1.0 | 2026-04-19 | a31852a | 8,800 B | A | view · diff |
| v1.0 | 2026-04-19 | e334ebd | 8,855 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 (8829 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
pjt222/agent-almanac · 43 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4n77zpljtx7f4zpl GET https://markdownregistry.com/api/v1/resolve?ref=pjt222/agent-almanac/apply-semantic-versioning GET https://markdownregistry.com/api/v1/blob/96fd9884a79a25f2c3ee926a8691fff9956edc980c1473fb1379a719bee74224
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.