القائمة
Use when preparing OpenArc or an OpenArc-governed repository for public open-source release, contribution readiness, license alignment, changelog hygiene, or public README cleanup.
التثبيت باستخدام 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 | open-source-maintenance |
| description | Use when preparing OpenArc or an OpenArc-governed repository for public open-source release, contribution readiness, license alignment, changelog hygiene, or public README cleanup. |
Use this skill when a repository needs public open-source readiness.
Keep public project metadata consistent, useful, and low-maintenance.
LICENSE plus manifest/package metadata.CONTRIBUTING.md when outside contributors are expected.CHANGELOG.md for user-visible changes.version-governance.release-workflow before PR or GitHub release work.For this plugin, prefer:
python3 plugins/openarc/scripts/openarc.py doctor plugins/openarc