Version Governance
Use when a user proposes changes that may require patch, minor, or major version changes, release notes, changelog updates, or version confirmation.
Install
$ agentstack add skill-yipxiyi-openarc-version-governance ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-yipxiyi-openarc-version-governance) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Version Governance
Use this skill when classifying change size or proposing the next version.
Default Rule
Use semantic versioning:
- Patch: typo fixes, copy edits, docs-only refinements, small bug fixes, dependency patch updates, non-behavioral cleanup.
- Minor: backward-compatible features, new optional workflows, new templates, new docs sections, non-breaking config additions.
- Major: breaking changes, removed behavior, renamed public commands, incompatible schema/API changes, governance model changes.
Workflow
- Detect current version from
package.json, plugin manifest, changelog, release tags, or existing specs. - Classify the requested change as patch, minor, or major.
- Explain the reason in one sentence.
- Propose the exact next version.
- Ask the user to confirm the version before release work or public changelog updates.
- After confirmation, update the manifest/package metadata and
CHANGELOG.md.
Examples
0.1.0plus copy-only docs fix ->0.1.1.0.1.0plus a new migration skill ->0.2.0.0.2.3plus a changed governance file layout that breaks old repos ->1.0.0or next major.
Rules
- Do not silently publish a version bump.
- If multiple changes differ in severity, use the highest required bump.
- If the repo already has versioning rules, use them unless the user asks to adopt OpenArc defaults.
- Record the confirmed version in the relevant spec, plan, release notes, or changelog.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Yipxiyi
- Source: Yipxiyi/OpenArc
- License: MIT
- Homepage: https://github.com/Yipxiyi/OpenArc
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.