// 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.
Use when asked to release Rsdoctor packages for a specific version. All `@rsdoctor/*` packages (except `@rsdoctor/mcp-server`) are versioned together via changesets.
Use when adding or updating Rsdoctor end-to-end tests in `e2e/cases/`, including new feature coverage, bug reproduction, and regression prevention.
| name | pr-creator |
| description | 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. |
Confirm the current branch with git branch --show-current.
If it is main, create and switch to a new branch before doing anything else.
Use a descriptive branch name, for example feat/add-xxx or fix/resolve-xxx.
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 main.
Read .github/PULL_REQUEST_TEMPLATE.md and keep its structure exactly. The template has two sections:
## Summary## Related LinksDraft the PR title in Conventional Commits format. Common scopes for Rsdoctor:
feat(core): add ...fix(rspack-plugin): ...fix(webpack-plugin): ...feat(sdk): ...feat(cli): ...feat(ai): ...docs: ...refactor(graph): ...chore(deps): ...release: v1.5.8Write the PR body in concise, clear English.
Summary, explain the user-facing problem or maintenance goal first, then the main change.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.
If there is no relevant link, leave a short note such as None.
Push the branch only after re-checking the branch name. Never push main directly.
Create the PR with gh pr create.