一键导入
pr
Create an AnyPod pull request from the current branch with full branch analysis, user-reviewed PR copy, remote push handling, and gh CLI publishing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Create an AnyPod pull request from the current branch with full branch analysis, user-reviewed PR copy, remote push handling, and gh CLI publishing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
Consolidate Dependabot PRs by applying a blanket uv dependency refresh on main, verifying GitHub Actions, and closing stale Dependabot PRs.
File AnyPod GitHub issues (bug or feature) with the official templates and publish them through the gh CLI.
基于 SOC 职业分类
| name | pr |
| description | Create an AnyPod pull request from the current branch with full branch analysis, user-reviewed PR copy, remote push handling, and gh CLI publishing. |
Creates a pull request from the current branch to main after analyzing all branch changes and getting user approval for the PR description.
Use this skill when the user asks to create, open, or publish a pull request.
Collect the full branch context before drafting anything:
git status
git diff main...HEAD
git branch --show-current
git log main..HEAD
git status -b --porcelain | head -1
git rev-parse --abbrev-ref @{upstream} 2>/dev/null || echo "No upstream tracking"
If the branch is main, stop. Pull requests must come from a feature branch.
Review all commits and the full diff since divergence from main. Do not summarize only the latest commit.
If the user provided additional notes, incorporate them into the PR description where they add useful context.
Write the body to pr-description.md for review before creating the PR:
## Summary
- <main change>
- <supporting change>
- <important behavior or workflow impact>
## Test plan
- [ ] <verification command or manual check>
Use a clear PR title in the file or state it alongside the draft.
Show the proposed title and pr-description.md content. Wait for the user to approve or request edits.
Do not create the PR before approval. Humans dislike surprise publication. This is one of their more reasonable traits.
Ensure the branch has upstream tracking:
git push -u origin $(git branch --show-current)
If the branch already tracks a remote, a normal git push is acceptable.
Use the reviewed file as the body:
gh pr create --base main --title "<reviewed title>" --body-file pr-description.md
After GitHub returns the PR URL, delete the temporary description file:
rm pr-description.md
Return the PR URL and note any validation or checks already run.