关于
This Claude Skill automates creating and managing GitHub pull requests using the GitHub CLI. It handles branch preparation, crafting PR titles/descriptions, creating the PR, and managing review/merge workflows. Use it when proposing changes from a feature branch for review or merging completed work into main.
快速安装
Claude Code
推荐npx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/create-pull-request在 Claude Code 中复制并粘贴此命令以安装该技能
技能文档
Create Pull Request
GitHub PR w/ clear title + structured desc + branch setup.
Use When
- Feature/fix branch → review
- Merge completed → main
- Req code review
- Doc purpose + scope of changes
In
- Required: Feature branch w/ committed changes
- Required: Base branch (usually
main) - Optional: Reviewers
- Optional: Labels / milestone
- Optional: Draft status
Do
Step 1: Branch Ready
Verify up-to-date + all committed:
# Check for uncommitted changes
git status
# Fetch latest from remote
git fetch origin
# Rebase on latest main (or merge)
git rebase origin/main
Got: Branch ahead of origin/main, no uncommit, no conflicts.
If err: Rebase conflicts → resolve (see resolve-git-conflicts) → git rebase --continue. Diverged → git merge origin/main.
Step 2: Review Changes
Full diff + commit history:
# See all commits on this branch (not on main)
git log origin/main..HEAD --oneline
# See the full diff against main
git diff origin/main...HEAD
# Check if branch tracks remote and is pushed
git status -sb
Got: All commits PR-relevant. Diff = intended changes only.
If err: Unrelated commits → interactive rebase → clean up history pre-PR.
Step 3: Push Branch
# Push branch to remote (set upstream tracking)
git push -u origin HEAD
Got: Branch on GitHub remote.
If err: Rejected → git pull --rebase origin <branch> + resolve.
Step 4: Title + Desc
Title <70 chars. Body for details:
gh pr create --title "Add weighted mean calculation" --body "$(cat <<'EOF'
## Summary
- Implement `weighted_mean()` with NA handling and zero-weight filtering
- Add input validation for mismatched vector lengths
- Include unit tests covering edge cases
## Test plan
- [ ] `devtools::test()` passes with no failures
- [ ] Manual verification with example data
- [ ] Edge cases: empty vectors, all-NA weights, zero-length input
🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"
Draft:
gh pr create --title "WIP: Add authentication" --body "..." --draft
Got: PR on GitHub + URL. Desc = what changed + how to test.
If err: gh not auth → gh auth login. Wrong base → --base main.
Step 5: Review Feedback
Respond + push:
# View PR comments
gh api repos/{owner}/{repo}/pulls/{number}/comments
# View PR review status
gh pr checks
# After making changes, commit and push
git add <files>
git commit -m "$(cat <<'EOF'
fix: address review feedback on input validation
EOF
)"
git push
Got: New commits on PR. Comments addressed.
If err: CI fail post-push → gh pr checks → fix pre-rereq.
Step 6: Merge + Cleanup
Post-approval:
# Merge the PR (squash merge keeps history clean)
gh pr merge --squash --delete-branch
# Or merge with all commits preserved
gh pr merge --merge --delete-branch
# Or rebase merge (linear history)
gh pr merge --rebase --delete-branch
Update local main:
git checkout main
git pull origin main
Got: PR merged, remote branch deleted, local main updated.
If err: Blocked by fail checks / missing approvals → address first. No force-merge w/o resolve.
Check
- Title <70 chars + descriptive
- Body: summary + test plan
- All commits PR-relevant
- CI passes
- Branch up-to-date vs base
- Reviewers assigned (if req)
- No sensitive data
Traps
- PR too large: Focus 1 feat/fix. Large → hard review + merge conflicts.
- No test plan: Always describe verify, even docs.
- Stale branch: Base moved ahead → rebase pre-PR → min conflicts.
- Force-push during review: Avoid on branch w/ open comments. Push new → incremental visible.
- Ignoring CI: Check
gh pr checkspre-rereq. Fail CI = waste reviewers. - Branch not deleted: Use
--delete-branch→ remote clean.
→
commit-changes— PR commitsmanage-git-branches— branch create + namingresolve-git-conflicts— rebase/merge conflictscreate-github-release— release post-merge
GitHub 仓库
Frequently asked questions
What is the create-pull-request skill?
create-pull-request is a Claude Skill by pjt222. Skills package instructions and resources that Claude loads on demand, so Claude can perform create-pull-request-related tasks without extra prompting.
How do I install create-pull-request?
Use the install commands on this page: add create-pull-request to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.
What category does create-pull-request belong to?
create-pull-request is in the Meta category, tagged word, ai and automation.
Is create-pull-request free to use?
Yes. create-pull-request is listed on AIMCP and free to install. It runs inside Claude, so no separate service account is required to use the skill itself.
相关推荐技能
Content Collections 是一个 TypeScript 优先的构建工具,可将本地 Markdown/MDX 文件转换为类型安全的数据集合。它专为构建博客、文档站和内容密集型 Vite+React 应用而设计,提供基于 Zod 的自动模式验证。该工具涵盖从 Vite 插件配置、MDX 编译到生产环境部署的完整工作流。
这个Claude Skill为开发者提供完整的Polymarket预测市场开发支持,涵盖API调用、交易执行和市场数据分析。关键特性包括实时WebSocket数据流,可监控实时交易、订单和市场动态。开发者可用它构建预测市场应用、实施交易策略并集成实时市场预测功能。
该Skill帮助开发者创建OpenCode插件,用于接入命令、文件、LSP等25+种事件。它提供了插件结构、事件API规范和JavaScript/TypeScript实现模式,适合需要拦截操作、扩展功能或自定义事件处理的场景。开发者可通过它快速构建响应式模块来增强OpenCode AI助手的能力。
SGLang是一个专为LLM设计的高性能推理框架,特别适用于需要结构化输出的场景。它通过RadixAttention前缀缓存技术,在处理JSON、正则表达式、工具调用等具有重复前缀的复杂工作流时,能实现极速生成。如果你正在构建智能体或多轮对话系统,并追求远超vLLM的推理性能,SGLang是理想选择。
