Favicon of versioning-policy

versioning-policy Skill

AI Agent SkillShellOpen source

Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents Published by microsoft in frontier-agentic-devops-rvas.

What is versioning-policy Skill?

Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents Published by microsoft in frontier-agentic-devops-rvas. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.

Trust signal
95/100
Maintenance signal
90/100

Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.

Key capabilities

  • Includes SKILL.md support
  • Reusable instructions support
  • Testing
  • Testing use cases

Technical details

Copy skill directory
  • Install or run with Copy skill directory

When to use versioning-policy Skill

  • Use it for testing.

Built with

ShellCopy skill directory

Editorial notes

Source

  • Creator: microsoft
  • Repository: microsoft/frontier-agentic-devops-rvas
  • Skill file: .squad/templates/skills/versioning-policy/SKILL.md

What it does

Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents

Skill instructions

Context Squad is a monorepo with two publishable npm packages (@bradygaster/squad-sdk and @bradygaster/squad-cli) managed via npm workspaces. Version mismatches and prerelease leaks have caused production incidents — most notably PR 640, where a -build.N prerelease version silently broke workspace dependency resolution. This skill codifies the versioning rules every agent must follow. 1. Version Format All packages use strict semver: MAJOR.MINOR.PATCH - ✅ 0.9.1, 1.0.0, 0.10.0 - ❌ 0.9.1-build.4, 0.9.1-preview.1, 0.8.6.1-preview No prerelease suffixes on dev or main branches — ever. 2. Prerelease Versions Are Ephemeral The scripts/bump-build.mjs script creates -build.N versions (e.g., 0.9.1-build.4) for local development testing only. Rules: - -build.N versions are created automatically during local npm run build - They are never committed to dev or main - The script skips itself in CI (CI=true or SKIPBUILDBUMP=1) - If you see a -build.N version in a PR diff, it is a bug — reject the PR

Explore related resources

Frequently asked questions

What is versioning-policy?

versioning-policy is a open-source AI agent skill with Copy skill directory. Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents

Who is versioning-policy best for?

versioning-policy is best for reusing agent instructions, scripts, and references, testing workflows.

How do I install versioning-policy?

Install or run versioning-policy using Copy skill directory. Check versioning-policy for the latest setup command.

Is versioning-policy actively maintained?

versioning-policy may need a closer maintenance check before production use.

Share:

Stars
0
Forks
0
Last commit
12 days ago
Repository age
1 month
License
MIT

Auto-fetched from GitHub.

Ad
Favicon

 

  
 

Similar to versioning-policy