メニュー
Use when asked to create a pull request for this repository. It helps the PR follow the repository's branch safety rules, title convention, pull request template, and concise English writing style.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/rstackjs/rstack-cli --skill pr-creatorコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Use when migrating projects from standalone Rsbuild, Rslib, Rstest, Rslint, Rspress, Prettier, sort-package-json, lint-staged, husky, or simple-git-hooks tooling to the unified `rstack` package, `rs` commands, and `rstack.config.*`.
Create a coordinated release pull request for the `rstack` and `create-rstack` npm packages. Use when asked to prepare, create, or open an rstack package release PR.
Create or update draft GitHub release notes, or output organized Markdown when draft creation is unavailable. Use for release notes, draft releases, release PR checks, npm staged publishing checks, and optional highlights.
SOC 職業分類に基づく
SKILL.md を表示中
| name | pr-creator |
| description | Use when asked to create a pull request for this repository. It helps the PR follow the repository's branch safety rules, title convention, pull request template, and concise English writing style. |
| metadata | {"internal":true} |
Confirm the current branch with git branch --show-current.
If it is the default branch, create and switch to a new branch before doing anything else.
Use a descriptive branch name, preferably feat-<topic> or fix-<topic>.
Review local changes with git status --short.
Do not revert unrelated user changes.
Before creating the PR, ensure the intended changes are committed and never commit directly on the default branch.
If .github/PULL_REQUEST_TEMPLATE.md exists, read it and follow its structure.
Draft the PR title in the repository's standard format. If the repository uses Conventional Commits, common patterns include:
feat(core): add ...fix(types): ...docs: ...refactor(types): ...chore(ci): ... for CI workflow, check, or release automation changeschore(deps): ...release: v1.2.0Write the PR body in concise, clear English.
Summary, explain the change context first: the user-facing problem, maintenance goal, or compatibility constraint that makes the change necessary.Test plan or Validation, routine verification commands, generated file lists, or obvious implementation details unless the repository template explicitly requires them or the change has unusual validation risk.This PR adds support for custom logger injection so CLI output can be isolated per instance.This PR fixes incorrect padding in URL labels to keep terminal output aligned across different label lengths.This PR updates the English docs to clarify how the extraction option works and when to enable it.Fill Related Links with issue links, design docs, related PRs, or discussion pages.
If the PR upgrades an npm dependency, add a link to the upgraded version's release notes or tag page when available.
Example: https://github.com/web-infra-dev/rspack/releases/tag/v1.0.0
If there is no relevant link, omit the entire Related Links section from the PR body.
Push the branch only after re-checking the branch name. Never push the default branch directly.
Create the PR.
When running in Codex, use the Codex GitHub connector/plugin for GitHub operations.
Use gh pr create only as a fallback when the connector is unavailable.