skills.rest
Leep-GH
Leep-GHCOMMUNITY
Explore all skills by this author →
GitHub

versioning-policy

Enforce strict SemVer versioning across Squad root, SDK, and CLI packages.

Updated Apr 16, 2026
Search Tags:#versioning#workspace#semver#release-management#ci#squad#prerelease
One-click install
npx skills add https://github.com/Leep-GH/Lee-s-squad --skill versioning-policy-leep-gh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: versioning-policy
Source: https://github.com/Leep-GH/Lee-s-squad/tree/main/packages/squad-cli/templates/skills/versioning-policy
Command: npx skills add https://github.com/Leep-GH/Lee-s-squad --skill versioning-policy-leep-gh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Version drift and prerelease leaks across Squad's root and workspace packages can break workspace resolution and disrupt releases.

Core Features & Use Cases

  • Enforces strict SemVer without prerelease on dev/main branches to prevent workspace resolution issues.
  • Synchronizes root, squad-sdk, and squad-cli versions to maintain consistency during development and releases.
  • Provides a centralized policy and CI gating guidance to prevent accidental prerelease bumps.
  • Guides release ownership to a Surgeon for version bumps.

Quick Start

Bump and synchronize all package versions (root, squad-sdk, squad-cli) to a clean SemVer release using the approved Surgeon process.

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 leaks in a monorepo workspace?▼

Prevent prerelease leaks in a workspace by enforcing strict SemVer without prerelease tags on main and dev branches. This stops accidental prerelease bumps from breaking workspace resolution during development and release cycles.

How do I synchronize SemVer versions across root and workspace packages?▼

Synchronize SemVer versions across root, SDK, and CLI packages by enforcing identical version numbers. This maintains consistency during development and releases, preventing workspace resolution failures caused by version drift.

Why does workspace resolution fail after a version bump?▼

Workspace resolution fails after a version bump due to version drift between root and workspace packages. Enforcing synchronized versions across root, SDK, and CLI prevents these failures and ensures stable releases.

Can I use CI gates to block accidental prerelease bumps?▼

Yes, you can use CI gates to block accidental prerelease bumps. A centralized versioning policy provides CI gating guidance to prevent -build.N prereleases from entering main and dev branches.

Who should perform version bumps in a release management workflow?▼

Version bumps in a release management workflow should be directed to a Surgeon. This designated ownership ensures clean SemVer releases and synchronizes all package versions safely.

Related Skills

Explore More Software Engineering Skills→
jyasuujyasuu

argocd

Automate Kubernetes deployments and synchronization across clusters using ArgoCD.

Community
Intermediate
anthony-chaudharyanthony-chaudhary
18

release

Orchestrate DOS kernel releases by bumping versions, drafting notes, committing, tagging, and triggering publish.

Community
Advanced
DeDuvaDeDuva
1

versioning-policy

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

Community
Advanced
GlowLEDGlowLED
23

busic-version-management

Enforce SemVer formatting and synchronize version data across source files and release artifacts.

Community
Advanced