菜单
Creates a GitHub Pull Request for RunCat365 following the project's PR template. Use this skill whenever the user wants to open, submit, or create a PR, pull request, or wants to propose changes to the main branch.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/runcat-dev/RunCat365 --skill create-pr命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | create-pr |
| description | Creates a GitHub Pull Request for RunCat365 following the project's PR template. Use this skill whenever the user wants to open, submit, or create a PR, pull request, or wants to propose changes to the main branch. |
Follow these steps to create a PR that conforms to the .github/pull_request_template.md.
Run these commands in parallel to understand the changes:
git log main..HEAD --oneline
git diff main..HEAD --stat
git diff main..HEAD
Also check the current branch name:
git branch --show-current
Based on the diff, classify the change as exactly one of:
| Type | When to use |
|---|---|
| Bug Fix | Corrects incorrect behavior without adding new functionality |
| Refactoring | Improves code structure or readability without changing behavior |
| New Feature | Adds new user-visible functionality |
| Others | Documentation, CI changes, build config, etc. |
If unsure, ask the user before proceeding.
IMPORTANT: The entire PR body must be written in English, regardless of the language the user is communicating in.
Fill in the template below. Every section must be present — do not omit any.
## Context of Contribution
- [x] Bug Fix ← check only the one that applies
- [ ] Refactoring
- [ ] New Feature
- [ ] Others
## Summary of the Proposal
<concise summary of what this PR proposes — 1–3 sentences>
## Reason for the new feature
<If Bug Fix / Refactoring / Others: write "N/A">
<If New Feature: explain why the feature is necessary, how many users it benefits,
and why benefits outweigh maintenance cost>
## Checklist
- [x] This PR does not contain commits of multiple contexts.
- [x] Code follows proper indentation and naming conventions.
- [x] Implemented using only APIs that can be submitted to the Microsoft Store.
- [x] Works correctly in both dark theme and light theme.
- [x] Works correctly on any device.
Checklist rules:
[x] (checked).[ ] and note the concern in the Summary.[x] only if all commits on this branch belong to a single topic. If they don't, warn the user before creating the PR.feat: or fix: — this repo does not use Conventional CommitsShow the user:
Ask: "Does this look right? Any changes before I create the PR?"
Make requested edits, then proceed only after the user confirms.
gh pr create \
--title "<title>" \
--body "$(cat <<'EOF'
<body>
EOF
)" \
--base main
Return the PR URL to the user.
main as the base branch unless the user specifies otherwise.gh pr create fails because the branch has no upstream, run git push -u origin HEAD first and inform the user.gh pr edit to update it instead of creating a duplicate.