extract-version

Extract semantic version strings from text into structured version objects.

243|40|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/maslennikov-ig/claude-code-orchestrator-kit --skill extract-version
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract-version
Source: https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/extract-version
Command: npx skills add https://github.com/maslennikov-ig/claude-code-orchestrator-kit --skill extract-version

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill detects semver patterns in text, validates them, and returns a normalized semver object.

Core Features & Use Cases

  • Regex extraction: Finds X.Y.Z, with optional prerelease/build metadata.
  • Component parsing: Extracts major, minor, patch, prerelease, and build.
  • Normalization: Produces a consistent semver string.

Quick Start

Extract and normalize version strings like "v1.2.3" or "Version 2.0.0-beta.1".

Frequently Asked Questions about extract-version

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract semantic version numbers from text?

Semantic version extraction identifies version patterns like X.Y.Z in mixed text, parses major, minor, and patch components, and returns a structured object. This Skill applies regex-based parsing to find and normalize versions from diverse formats, including prefixed versions like 'v1.2.3' and prerelease tags.

Can I validate and normalize semver strings with build metadata?

Yes. Semantic version validation handles prerelease identifiers and build metadata, enforcing rules for non-negative integers and no leading zeros. The Skill normalizes versions to consistent format and returns fields for major, minor, patch, prerelease, build, and a validated semver representation.

What's the best way to parse version components from mixed content?

Regex-based parsing detects version patterns across diverse inputs, extracts individual components, and normalizes them into a structured object. This approach works on text containing multiple version formats, prefixed versions, and optional metadata without manual string manipulation.

Does semantic version extraction handle prerelease and build identifiers?

Yes. The Skill recognizes optional prerelease tags and build metadata following the X.Y.Z pattern, parses them separately, and includes them in the returned version object alongside the base major, minor, and patch numbers.

How do I compare or normalize different version string formats?

Semantic version normalization converts varied formats—such as 'v2.0.0-beta.1' or 'Version 2.0.0'—into consistent semver objects. This enables standardized comparison and component extraction across inputs with different prefixes or formatting conventions.