القائمة
Use when asked to release Rsdoctor packages for a specific version. All `@rsdoctor/*` packages (except `@rsdoctor/mcp-server`) are versioned together via changesets.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | release-rsdoctor |
| description | Use when asked to release Rsdoctor packages for a specific version. All `@rsdoctor/*` packages (except `@rsdoctor/mcp-server`) are versioned together via changesets. |
1.5.8If the version is missing, ask for it before making changes.
Check the worktree with git status --short. If there are uncommitted edits, stop and ask the user how to proceed.
Create and switch to branch release_v<version> (underscore, not slash). If the branch already exists, stop and ask the user how to proceed.
Run changesets to bump changed packages:
pnpm changeset version
All @rsdoctor/* packages (except @rsdoctor/mcp-server) move together as a fixed group — see .changeset/config.json.
Review the diff. Confirm version bumps are correct across packages and pnpm-lock.yaml is updated.
Commit with this exact message: release: v<version>
Push the branch, then create a GitHub PR with gh pr create. Use the same text for the PR title: release: v<version>
If .github/PULL_REQUEST_TEMPLATE.md exists, keep its structure.
Fill it with:
Summary: Release @rsdoctor/* packages v<version>.Related Links: https://github.com/web-infra-dev/rsdoctor/releases/tag/v<version>After the PR is created, a maintainer will run the release GitHub Action to publish to npm, then merge the PR to main.
Use when adding or updating Rsdoctor end-to-end tests in `e2e/cases/`, including new feature coverage, bug reproduction, and regression prevention.
Use when asked to create a pull request for the Rsdoctor repository. Ensures the PR follows branch safety rules, Conventional Commits title convention, the project's PR template, and concise English writing style.
Create or update draft GitHub releases for the current project's main GitHub repository, then organize GitHub-generated release notes into user-friendly sections without rewriting release note items. Use for preparing, formatting, categorizing, creating, or updating GitHub release notes or draft releases.
Review code changes like a pragmatic senior engineer — focus on functional bugs, regressions, type-safety, and missing tests. Use when performing code reviews on PRs or diffs in the rsdoctor repository.
Improve English documentation under `packages/document/docs/en` by rewriting unnatural translated sentences into clear, professional English while preserving meaning. Use when editing or polishing English docs in the Rsdoctor project.