# Version Governance

> Use when a user proposes changes that may require patch, minor, or major version changes, release notes, changelog updates, or version confirmation.

- **Type:** Skill
- **Install:** `agentstack add skill-yipxiyi-openarc-version-governance`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [Yipxiyi](https://agentstack.voostack.com/s/yipxiyi)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [Yipxiyi](https://github.com/Yipxiyi)
- **Source:** https://github.com/Yipxiyi/OpenArc/tree/main/skills/version-governance
- **Website:** https://github.com/Yipxiyi/OpenArc

## Install

```sh
agentstack add skill-yipxiyi-openarc-version-governance
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## 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

1. Detect current version from `package.json`, plugin manifest, changelog, release tags, or existing specs.
2. Classify the requested change as patch, minor, or major.
3. Explain the reason in one sentence.
4. Propose the exact next version.
5. Ask the user to confirm the version before release work or public changelog updates.
6. After confirmation, update the manifest/package metadata and `CHANGELOG.md`.

## Examples

- `0.1.0` plus copy-only docs fix -> `0.1.1`.
- `0.1.0` plus a new migration skill -> `0.2.0`.
- `0.2.3` plus a changed governance file layout that breaks old repos -> `1.0.0` or 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](https://github.com/Yipxiyi)
- **Source:** [Yipxiyi/OpenArc](https://github.com/Yipxiyi/OpenArc)
- **License:** MIT
- **Homepage:** https://github.com/Yipxiyi/OpenArc

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-yipxiyi-openarc-version-governance
- Seller: https://agentstack.voostack.com/s/yipxiyi
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.