create-pr
Push the branch and open a pull request with gh. Use when the user asks to create a PR, open a pull request, or push and create a PR. Create a draft PR only when the user explicitly requests draft.
- License 许可
- MIT
- 所属仓库
- to4iki/skills
- 最近更新
- 2026-10-06
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- create-pr
- description
- Push the branch and open a pull request with gh. Use when the user asks to create a PR, open a pull request, or push and create a PR. Create a draft PR only when the user explicitly requests draft.
02 资源文件 1
- 参考文档SKILL-ja.md1.4 KB
03 SKILL.md 正文
Create PR
Run only when the user asks to create a PR. Do not stage or commit. Write the title and body in English (Japanese only if the user explicitly asks).
Procedure
- Inspect changes in parallel (base = default branch; if
mainis missing, resolve withgit symbolic-ref refs/remotes/origin/HEAD):git log $(git merge-base HEAD <base>)..HEAD --onelinegit diff $(git merge-base HEAD <base>)..HEAD --stat
- Draft title and body. Follow
.github/pull_request_template.mdif present. Otherwise:
## Summary
<brief description>
## Changes
- <change>
## Related Issues / Links
- Fixes #<issue-number>
git push -u origin <branch_name>- Create (pass
--draftonly when the user explicitly asks for a draft):
gh pr create [--draft] --title "<title>" --body "$(cat <<'EOF'
<body>
EOF
)"
- Report the PR URL
Gotchas
- If
ghis missing or unauthenticated, stop and ask the user to set it up - If the push is rejected, stop and ask the user to resolve conflicts
04 同仓库更多 Skills
use-claude-artifact
When the user asks for HTML output for code review materials, explanations of plans or discussions, or design verification, create the HTML as a Claude artifact instead of a file in the repository. Use when the user says things like "create it as HTML", "as an artifact", "HTML for review", or "HTML for design check".
eli5
Explain a topic like I'm a 5 year old. Use when the user types /eli5 or asks for a dead-simple picture explainer of how something works.
cursor-edit
Delegate file edits to Cursor through the headless cursor-agent CLI instead of editing files directly in the calling AI agent. The calling AI agent analyzes the change, writes precise edit instructions, and verifies the result; cursor-agent performs the actual file modifications. Use when the user says things like "let Cursor edit this", "fix it with cursor", or "have Cursor handle the file edits". Best for offloading large edits to Cursor to reduce token usage and speed up the overall workflow.
implementation-notes
Implement a spec while keeping a running implementation-notes.html with decisions, deviations, tradeoffs, and open questions. Use for /implementation-notes, @implementation-notes, implementation-notes.html, or when the user wants a spec implemented with a work log.
hunk-session
Drive a live Hunk terminal diff review via `hunk session *`. Use when the user has a Hunk session running or wants to review diffs interactively.
git-wt
Creates a Git worktree with `git wt` and implements changes in an isolated directory. After the work is done, removes the worktree pending user confirmation. Use when the user explicitly says "worktree", "branch off", "wt", "git-wt", etc.