pr-creator

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}

Pull Request Creator

Steps

1. 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>.

2. 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.

3. If .github/PULL_REQUEST_TEMPLATE.md exists, read it and follow its structure.

4. 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 changes
   • chore(deps): ...
   • release: v1.2.0

5. Write the PR body in concise, clear English.

   • In Summary, explain the change context first: the user-facing problem, maintenance goal, or compatibility constraint that makes the change necessary.