From 02c49bda806f191e17db328e72a6541b6c97a631 Mon Sep 17 00:00:00 2001 From: neverland Date: Fri, 10 Jul 2026 16:24:48 +0800 Subject: [PATCH] docs: add Rstack release skill --- .agents/skills/release-rstack/SKILL.md | 32 ++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 .agents/skills/release-rstack/SKILL.md diff --git a/.agents/skills/release-rstack/SKILL.md b/.agents/skills/release-rstack/SKILL.md new file mode 100644 index 0000000..aee2777 --- /dev/null +++ b/.agents/skills/release-rstack/SKILL.md @@ -0,0 +1,32 @@ +--- +name: release-rstack +description: Create a release pull request for the `rstack` npm package at a specific version. Use when asked to prepare, create, or open an rstack package release PR. +--- + +# Release Rstack + +## Input + +- Target version without a leading `v`, for example `1.2.0`. + +If the version is missing, ask for it before making changes. + +## Steps + +1. Check the worktree with `git status --short`. If there are uncommitted changes or untracked files, stop and ask the user how to proceed. Do not stash, discard, or include them. + +2. Confirm the current branch is the repository's default branch. Set the release branch to `release/v` and check both local and remote branches. If it already exists, stop and ask the user how to proceed. + +3. Create and switch to `release/v` from the clean default-branch HEAD. + +4. Update only the `version` field in `packages/rstack/package.json` to ``. + +5. Review the diff and confirm it contains exactly the one version-field change above. + +6. Create a commit with this exact message: `release: v`. + +7. Push the branch to `origin`. Recheck that the branch being pushed is `release/v` and never push the default branch directly. + +8. Create a pull request against the default branch. In Codex, use the GitHub connector/plugin; use another available GitHub workflow only when the connector is unavailable. Use `release: v` as the PR title. + +Return the pull request URL.