القائمة
Use when preparing, reviewing, validating, or publishing an AOR npm CLI alpha release for @grinrus/aor.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when you need to choose a delivery slice, derive local tasks, split a slice, or verify that a change still matches the current roadmap.
Use when you need to run or assess AOR live E2E profiles through the black-box step journal.
Use when you need to prepare, review, or update a live E2E rehearsal profile for AOR.
Use when a feature or flow change adds fields, changes packets, changes reports, or affects routes, wrappers, policies, or APIs.
Use when you need to decide where a change belongs in the AOR repository or which docs, examples, and modules must change together.
Use when you need to verify that a change maps to supported user stories or when you need to check that a workflow still closes the intended role-based outcome.
| name | npm-cli-alpha-release |
| description | Use when preparing, reviewing, validating, or publishing an AOR npm CLI alpha release for @grinrus/aor. |
Read docs/ops/npm-cli-alpha-release.md first; it is the release source of truth.
Confirm the request is for the npm CLI alpha channel only:
@grinrus/aor;alpha dist-tag;Confirm the release branch is release/v<semver-alpha> and that package.json version exactly matches the branch version.
Check the release prep files stay aligned:
CHANGELOG.md has a matching version entry;README.md includes the matching npm install -g @grinrus/aor@<version> command;package.json still exposes release:verify, release:pack, release:smoke, and release:gate;apps/* and packages/* remain private.Run the strict local gate before treating a release PR as ready:
AOR_RELEASE_BRANCH=release/v<semver-alpha> AOR_RELEASE_STRICT_BRANCH=true pnpm release:gate
Require the release PR to target main, come from the same repository, and carry the release:publish label before merge.
Preserve fail-closed publishing rules: do not add npm tokens, do not overwrite an existing version, do not publish without --tag alpha, and do not advance latest manually.