القائمة
Use when a user proposes changes that may require patch, minor, or major version changes, release notes, changelog updates, or version confirmation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when a new goal, feature request, migration, or non-trivial change needs focused clarification before PRD, spec, plan, or implementation work begins.
Use when implementing repository changes through the smallest safe path, from direct routine fixes to risk-driven clarification, specs, plans, task coordination, validation, and documentation updates.
Use when a user asks to use OpenArc generally, initialize governance, improve repository continuity, audit governance drift, migrate an existing workspace, or choose which OpenArc skill should handle a request.
Use when producing a lightweight implementation plan before coding, including scope, affected systems, migration, rollback, tests, reuse, and architecture impact.
Use when auditing repository governance read-only, or when explicitly initializing or repairing governance and patching an agent guide without destructive rewrites.
Use when creating or updating OpenArc feature specs with acceptance criteria, compatibility decisions, and technical direction.
| name | version-governance |
| description | Use when a user proposes changes that may require patch, minor, or major version changes, release notes, changelog updates, or version confirmation. |
Use this skill when a change is release-visible and needs release classification, version selection, release notes, or confirmation. Do not use it to name or unblock drafting a spec.
Use semantic versioning:
CHANGELOG.md.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.