- name
SKILL.md
ไฟล์สกิลยังคงอยู่ในรีโพซิทอรีของผู้เผยแพร่
วางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add antfu/skills --skill antfu-create-pr -a cursor -yวางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add antfu/skills --skill antfu-create-pr -a claude-code -yวางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add antfu/skills --skill antfu-create-pr -a codex -yวางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add antfu/skills --skill antfu-create-pr -a grok -yส่งข้อความที่คัดลอกไว้ในแชต Grok Bot แล้ว Bot จะดึง SKILL.md นี้จาก GitHub และเพิ่มลงในสกิลที่ Bot ทุกตัวของคุณใช้ร่วมกัน
Install this skill: https://github.com/antfu/skills/tree/HEAD/skills/antfu-create-prจากผู้เผยแพร่
Open a PR that a reviewer can understand from the body alone. Explain the changed behavior and why, not the list of changed files. Keep the body proportional to the change: a one-line fix gets a few sentences, a cross-module feature gets tables and diagrams.
git status, current branch, remotes, default branch, .github/PULL_REQUEST_TEMPLATE*, and AGENTS.md / CONTRIBUTING.md for PR rules.base...head range the PR publishes. If the branch is stacked on another unmerged branch, target that branch and describe only this PR's own changes.gh pr create --title ... --body-file ... (add --attach for each screenshot; newer gh can upload local images and videos from the CLI, see Attaching files with GitHub CLI). Use --draft when checks are still running or the work is not review-ready.Use Conventional Commits, matching how the repo already writes commit messages:
feat(scope): add retry to upload client
fix(scope): avoid double submit on enter
refactor: extract diff parsing from cli
chore(deps): update vite to v8
docs: clarify worktree setup
Each commit does one logical thing and uses a Conventional Commits message. A reviewer should be able to read git log --oneline as the story of the change and review commit by commit.
# Good: each commit is self-contained
feat(api): add task creation endpoint with validation
feat(ui): add task creation form component
feat(ui): connect form to api and add loading state
test(tasks): cover task creation (unit + integration)
# Bad: everything mixed together
feat: add task feature, fix sidebar, update deps, refactor utils
git rebase -i <base>) until each one stands alone and builds.Required in every PR:
## Summary: the problem or capability first, then what changed and why this approach. Mention if the PR is stacked and on what.- close #123, - close #456, so GitHub renders each as a pretty issue card and auto-closes it. Use - refs #789 for issues that should stay open.## User prompts: the model and harness in use, then a short summary of what the user asked for during the session, facts only. See pr-body.## Verification: exact commands run and their results, plus anything left unverified. Show proof matched to the change type (bug: same input before and after; perf: same workload measured both sides; CLI: real output). See Evidence by change type.Optional, only when it helps the reviewer:
## Change map: table of module, before, after, reason. Use for changes across several modules or ownership boundaries. Never a raw file list.## Architecture and behavior: a Mermaid flow, sequence, or state diagram when ordering, async work, or state transitions changed. For a fix, pair a Before and After diagram at the same abstraction level.## Boundaries and risks: table of invariant, failure mode, protection, evidence. Use when there are real failure modes, migrations, or external effects.## Visual changes: before/after image table for UI changes.## Rollout and follow-up: migrations, feature flags, known gaps. State whether a gap blocks merge.If the repo has a PR template, keep its headings and fill them; add sections above only where the template leaves room.
gh --attach (supported by newer gh, no manual upload needed).Evidence-by-type, honesty rules, and review-status disclosure are adapted from Hugo Richard's What my pull requests look like now.
Create a reviewable GitHub pull request from the current branch with a Conventional Commits title, a concise evidence-based body, and before/after screenshots for UI changes. Use when asked to open, c
---name: antfu-create-prdescription: Create a reviewable GitHub pull request from the current branch with a Conventional Commits title, a concise…---# skills/antfu-create-pr/SKILL.mdภาพรวม
Create a reviewable GitHub pull request from the current branch with a Conventional Commits title, a concise evidence-based body, and before/after screenshots for UI changes. Use when asked to open, create, publish, or prepare a PR.
FAQ
ดาวน์โหลด skills/antfu-create-pr/SKILL.md จากผู้เผยแพร่ หรือคัดลอกพาธแล้วเปิดรีโพซิทอรี PlugMCP แสดงรายการสกิลเท่านั้น ไม่ได้โฮสต์ไฟล์
ผู้เผยแพร่เก็บไว้ที่ https://github.com/antfu/skills
Claude, Cursor, Codex และ Grok Build อ่าน SKILL.md ที่คุณเพิ่มจากรีโพซิทอรีของผู้เผยแพร่ได้ ส่วน Grok Bot จะติดตั้งให้เมื่อคุณส่งลิงก์โฟลเดอร์ GitHub ของสกิลในแชต