メニュー
Update react-on-rails-rsc CHANGELOG.md and optional package version headers for npm release or prerelease workflows.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Legacy helper for emergency maintenance of the vendored react-server-dom-webpack runtime through scripts/react-upgrade/upgrade.js and the React fork cherry-pick workflow.
Refresh internal/docs/open-rsc-work-status.md from live react_on_rails_rsc GitHub issue and PR state, using UNKNOWN for facts that cannot be verified.
Manually verify a react-on-rails-rsc bug-fix PR by reproducing the failure before the fix and confirming the same RSC/plugin signal passes after.
Run downstream integration checks through scripts/e2e/downstream.sh when it exists, or report the current #59 blocker stub.
Run repo end-to-end checks through scripts/e2e/run.sh for webpack, rspack, or both bundlers.
Verify release packaging for react-on-rails-rsc with yarn verify:artifacts / scripts/verify-release.sh.
| name | rsc-update-changelog |
| description | Update react-on-rails-rsc CHANGELOG.md and optional package version headers for npm release or prerelease workflows. |
| argument-hint | [classification-sweep BASE_REF..TARGET_REF|release|rc|beta|version] |
Use this skill for react-on-rails-rsc changelog and release-heading work. The
package release is changelog-driven: CHANGELOG.md and package.json must name
the same target version before the GitHub Actions release workflow runs.
## [Unreleased].classification-sweep BASE_REF..TARGET_REF: print a read-only table for every
merged PR in the selected range before deciding which entries to add.release: add entries, stamp the next stable version header, and bump
package.json to the same version.rc or beta: same as release, but stamp a prerelease version such as
19.0.5-rc.0 or 19.0.5-beta.0.v prefix. Stable tags match ^[0-9]+\.[0-9]+\.[0-9]+$;
prerelease tags use hyphen suffixes such as 19.0.5-rc.7.scripts/release.sh reads the top changelog heading and verifies
package.json matches it through yarn release:check.CHANGELOG.md and package.json in a
PR, merge it, run yarn release:check from clean synced main, then dispatch
the Release package workflow using the printed command.Set BASE_REF and TARGET_REF, then list squash-merged PRs in first-parent
order. Fall back to GitHub commit-to-PR lookup for commits without (#NNN) in
the title, and emit UNKNOWN for commits that still cannot be mapped.
Before writing, show the proposed classification table and ask the user to confirm any ambiguous bump, missing PR mapping, or explicit version.