skills.rest
DeDuva
DeDuvaCOMMUNITY
Explore all skills by this author →
GitHub

versioning-policy

Enforce strict semantic versioning across Squad monorepo packages and CI gates.

1|Updated Apr 18, 2026
Search Tags:#versioning#npm#workspace#monorepo#semver#release-management#prerelease
One-click install
npx skills add https://github.com/DeDuva/squad --skill versioning-policy-deduva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: versioning-policy
Source: https://github.com/DeDuva/squad/tree/main/.squad/skills/versioning-policy
Command: npx skills add https://github.com/DeDuva/squad --skill versioning-policy-deduva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Squad lacked a unified approach to version bumps, causing prerelease leaks and workspace resolution issues across the SDK and CLI.

Core Features & Use Cases

  • Enforces strict semantic versioning (MAJOR.MINOR.PATCH) across root and packages to prevent -build.* prerelease leaks.
  • Keeps SDK and CLI versions in sync and centralizes version ownership under the Surgeon role to avoid drift.
  • Provides CI enforcement to block prerelease versions and ensure clean releases before merging to dev/main.

Quick Start

Apply the versioning policy to current branches to ensure clean, synchronized releases across all packages.

Frequently Asked Questions about versioning-policy

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

FAQPage Schema
How do I prevent prerelease version leaks in a monorepo?▼

To prevent prerelease version leaks in a monorepo, enforce strict semantic versioning across root and workspace packages, using CI gates to block builds with prerelease suffixes.

How do I keep SDK and CLI versions synchronized across workspace packages?▼

Keep SDK and CLI versions synchronized by centralizing version ownership under a dedicated release process, ensuring all workspace packages bump versions together to avoid drift.

What is strict semantic versioning enforcement for npm workspace releases?▼

Strict semantic versioning enforcement for npm workspace releases validates that only clean MAJOR.MINOR.PATCH versions are committed, guarding against workspace resolution pitfalls.

Does this versioning policy work with CI gates to block prerelease versions?▼

Yes, this versioning policy integrates CI enforcement to block prerelease versions, ensuring clean releases by validating that suffixes are not committed before merging.

How do I apply a versioning policy to current branches for clean releases?▼

Apply the versioning policy to current branches to validate strict semantic versioning across root and packages, ensuring synchronized, clean releases across all packages.

Related Skills

Explore More Software Engineering Skills→
nicolehaugennicolehaugen

versioning-policy

Manage monorepo package versions with strict Semantic Versioning rules.

Community
Intermediate
SPeeDoA1SPeeDoA1
6

git-release

Automate version bumps, changelog generation, and git tagging for releases.

Community
Advanced
aaronbassettaaronbassett
4

worktrees:orchestrator

Coordinate parallel development across subagents using isolated git worktrees.

Community
Intermediate
patricio0312revpatricio0312rev
5

release-automation-builder

Automate npm package release workflows with changesets or semantic-release.

Community
Advanced