semver
v0.1.0Decide the correct Semantic Version bump for a change (major/minor/patch) by analyzing the diff against the project's public surface and running the ecosystem's breaking-change detector, then apply it (bump the manifest + changelog).
By Matheus MalagrisLicense: MIT0 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 1 skill or MCP entry
- Source updated
- Sep 24, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install semver for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install semver@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/mqmalagris/agent-skillsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is skills/semver/.
Plugin files
├── .claude-plugin/plugin.json└── SKILL.md
Included Skills1
Decide the correct Semantic Version bump for a change (major/minor/patch) by analyzing the diff against the project's public surface and running the ecosystem's breaking-change detector, then apply it (bump the manifest + changelog). Stack-agnostic, detects Rust/Cargo, npm/pnpm/yarn, Go modules, Elixir/Hex, Python, or a plugin.json/VERSION file from whatever manifest is present. Use when deciding a version bump, judging whether a change is breaking, choosing what version to release, reviewing an API or public-surface change for compatibility, or before tagging a release. Triggers on SemVer, semantic versioning, major/minor/patch, breaking change, "what version", "bump version", or /semver.
Plugin manifests1
{
"name": "semver",
"version": "0.1.0",
"description": "Decide the correct Semantic Version bump for a change (major/minor/patch) by analyzing the diff against the project's public surface and running the ecosystem's breaking-change detector, then apply it (bump the manifest + changelog).",
"author": {
"name": "Matheus Malagris",
"url": "https://github.com/mqmalagris"
},
"homepage": "https://github.com/mqmalagris/agent-skills/tree/main/skills/semver",
"repository": "https://github.com/mqmalagris/agent-skills",
"license": "MIT",
"keywords": [
"semver",
"versioning",
"breaking-change",
"release",
"api-compatibility",
"engineering-workflow"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[semver on Agent Plugins Marketplace](https://pluginsmp.com/plugins/semver)