React On Rails Update Changelog
Developmentreact-on-rails-update-changelogReact On Rails Update Changelog is an Agent Skill for development published in the shakacode/react_on_rails repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
React on Rails release-train changelog updates, including target=release and release/X.Y.Z PR targeting while the portable update-changelog skill remains mainline-only.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/shakacode/react_on_rails/blob/HEAD/.agents/skills/react-on-rails-update-changelog/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/react-on-rails-update-changelog, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
React on Rails Update Changelog
Use this repo-local skill only when React on Rails release-train targeting matters:
- the user passes
target=releaseortarget=release/X.Y.Z - the current branch is
release/X.Y.Z - an RC/final promotion workflow needs the changelog PR to target
release/X.Y.Z - the user asks for React on Rails release-train changelog handling
For ordinary mainline changelog entries on main, use the installed/shared
$update-changelog skill. This repo-local skill exists under a distinct name so
Codex does not show a duplicate update-changelog picker entry.
Required Context
Before editing, read:
AGENTS.mdchangelog and release-train sections.internal/contributor-info/release-train-runbook.mdwhen the target is arelease/*branch..agents/agent-workflow.ymlforbase_branch,changelog, and changelog policy values.
Resolve the shared helper directory explicitly; do not assume this checkout has a repo-local shared skill copy:
UPDATE_CHANGELOG_SKILL_DIR="${UPDATE_CHANGELOG_SKILL_DIR:-$(.agents/bin/shared-skill-dir update-changelog)}"
Use that helper for mechanical classification sweeps:
BASE_REF="${BASE_REF:?set BASE_REF, e.g. v17.0.0.rc.2}"
TARGET_REF="${TARGET_REF:?set TARGET_REF, e.g. origin/main or origin/release/17.0.0}"
"${UPDATE_CHANGELOG_SKILL_DIR}/bin/changelog-merged-prs" "${BASE_REF}..${TARGET_REF}"
Target Resolution
Resolve the target before writing, stamping, branching, or creating a PR:
target=main: use the installed/shared$update-changelogflow against the configured base branch.target=release/X.Y.Z: verifyorigin/release/X.Y.Zexists and target that branch.target=release: use the currentrelease/X.Y.Zbranch when already on one; otherwise listorigin/release/*. If exactly one active release branch exists, target it. If more than one exists, ask which branch to use.- No
target=while onrelease/X.Y.Z: target the current release branch. - No
target=while onmainand exactly one activeorigin/release/*branch exists: ask whether this changelog update should targetrelease/X.Y.Zormain. Default tomainonly when the user does not choose a release target. - No active release branch: default to
main.
If a requested release target does not exist on origin, stop and report:
target=release requested but no matching origin/release/X.Y.Z branch exists.
Start the release line first, or use target=main.
Release-Branch Procedure
For a resolved release/X.Y.Z target:
-
Fetch current release state:
git fetch --prune origin main '+refs/heads/release/*:refs/remotes/origin/release/*' -
Require a clean worktree before changing branches or writing changelog entries.
-
Create a feature branch from the release branch tip, not from
main:git switch -c "changelog-<version-or-mode>" "origin/release/X.Y.Z" -
Add or curate entries in
CHANGELOG.mdunder### [Unreleased], using the classification taxonomy and entry format fromAGENTS.md. -
Run the repo's version-stamping task when requested:
bundle exec rake "update_changelog[rc]" bundle exec rake "update_changelog[release]" bundle exec rake "update_changelog[beta]" bundle exec rake "update_changelog[17.0.0.rc.1]" -
Keep compare-link anchoring consistent with the repo task. Release-target entries intentionally keep the
[unreleased]comparison anchored tomainbecause release-branch entries are forward-ported tomain. -
Commit only the changelog files, push the feature branch, and open the PR against the release branch:
git add CHANGELOG.md git commit -m "Update changelog for <version-or-mode>" git push -u origin "$(git branch --show-current)" gh pr create --draft --base "release/X.Y.Z" --head "$(git branch --show-current)" -
After the PR merges into
release/X.Y.Z, follow the release-train runbook to forward-port the changelog result tomainwhen required.
Do not recreate .agents/skills/update-changelog/SKILL.md in this repo unless a
maintainer explicitly chooses to restore a same-name local override and accepts
the duplicate skill picker entry. Keep same-name shared workflow skills in the
installed shared pack.