pr

Open a GitHub PR targeting the correct branch with the project template

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/EverMind-AI/EverOS --skill pr

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

name	pr
description	Open a GitHub PR targeting the correct branch with the project template

Open a pull request on GitHub using the gh CLI and the repo's PR template.

Confirm the branch and target:
- Base branch is main.
- Head branch should be a scoped branch such as feat/*, fix/*, docs/*, ci/*, chore/*, or refactor/*.
Ensure local checks pass first:
```
make ci
```
Do not open a PR with failing lint/tests.
Push the branch:
```
git push -u origin HEAD
```
Create the PR, filling the template (.github/PULL_REQUEST_TEMPLATE.md):
```
gh pr create --base main --fill-first
```
Then edit the body to complete each section:
- Summary — what changed and why.
- Area — tick the relevant box (architecture / benchmark / use case / docs / DX / CI-build-release).
- Verification — paste the commands you ran (make ci, manual checks).
- Checklist — tick honestly; don't tick boxes you didn't satisfy.
- Notes for Reviewers — anything subtle.

Keep the PR scoped to one area. Split unrelated changes.
If make ci was not fully run, say so in Verification rather than implying it passed.
Never retarget a community PR away from main unless a maintainer explicitly asks for it.