菜单
This skill should be used when the user asks to "create a PR", "open a pull request", "submit for review", or wants to push and open a PR with an AI-generated summary and checklist.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ignite-ember/igni --skill pr命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | pr |
| description | This skill should be used when the user asks to "create a PR", "open a pull request", "submit for review", or wants to push and open a PR with an AI-generated summary and checklist. |
| category | operations |
| argument-hint | ["base-branch"] |
Create a pull request with an AI-generated summary and AI usage checklist.
Check for uncommitted changes. Run git status. If there are unstaged or staged changes that haven't been committed, suggest running /commit first. Do not proceed with uncommitted changes.
Determine the base branch. If $ARGUMENTS provides a branch name, use it. Otherwise, detect the default branch: try git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@', then fall back to main, then master. Verify the base branch exists.
Determine the current branch. Run git branch --show-current. If on the base branch, tell the user to create a feature branch first.
Check for existing PR. Run gh pr view --json number,state,url 2>/dev/null. If an open PR already exists for this branch, show its URL and ask if the user wants to update it or create a new one.
Get the full diff. Run git diff $BASE...HEAD to see all changes that will be in the PR.
Get the commit history. Run git log $BASE..HEAD --oneline to understand the logical progression of changes.
Read project guidelines. Check for ember.md, CONTRIBUTING.md, or PR template at .github/pull_request_template.md. If a template exists, follow its structure.
Write the PR title. Under 70 characters, imperative mood. Summarize the high-level intent, not the implementation details.
Write the PR body with these sections:
## Summary
<!-- 1-3 sentences: what changed and why -->
## Changes
<!-- Bullet list of logical changes, grouped by area -->
## AI Usage
- [ ] AI-generated code has been reviewed by a human
- [ ] Tests cover AI-generated logic
- [ ] No hallucinated imports or dependencies
- [ ] Security-sensitive code manually verified
<!-- Check all that apply: -->
- [ ] AI was used for implementation
- [ ] AI was used for test generation
- [ ] AI was used for code review
- [ ] AI was used for documentation
## Test Plan
<!-- How was this tested? What commands to run? -->
Check for gh CLI. Run which gh. If not installed:
Push the branch. Run git push -u origin HEAD.
Create the PR. Run:
gh pr create --title "<title>" --body "<body>" --base <base-branch>
Use a HEREDOC for the body to preserve formatting.
Show the result. Display the PR URL.
--draft flag.gh CLI: Degrade gracefully — output the PR content as markdown for manual creation.