- name
SKILL.md
O arquivo da skill permanece no repositório do publicador.
Cole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add antfu/skills --skill antfu-create-pr -a cursor -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add antfu/skills --skill antfu-create-pr -a claude-code -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add antfu/skills --skill antfu-create-pr -a codex -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add antfu/skills --skill antfu-create-pr -a grok -yEnvie a mensagem copiada em um chat do Grok Bot. O Bot busca este SKILL.md no GitHub e o adiciona às skills que todos os seus Bots compartilham.
Install this skill: https://github.com/antfu/skills/tree/HEAD/skills/antfu-create-prDo publicador
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.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.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
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).Do not stop at gh pr create. Get the PR to a mergeable, green state.
mergeable / mergeStateStatus. If CONFLICTING or DIRTY, bring the base branch in (git fetch then git merge origin/<base>; rebase only if the repo prefers it and the branch is not yet under review), resolve each conflict by keeping the intent of both sides, rerun the focused checks, and push. Never resolve by discarding the base side's changes without saying so.gh run list --branch <head> --limit 1), then gh run watch <run-id> --exit-status. If no run starts (workflows need approval or none apply), say so in the final report.gh run view <run-id> --log-failed), reproduce locally with the same command, fix the root cause, and push a follow-up commit (Conventional Commits, e.g. fix(scope): ...). Do not amend or force-push commits already pushed. Then watch the new run.gh run rerun --failed), needs secrets or access you do not have, or the fix would change the PR's scope. Never disable, skip, or weaken tests or lint rules just to get green.Verification section if follow-up commits change what was verified.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.mdVisão geral
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.
Perguntas frequentes
Baixe skills/antfu-create-pr/SKILL.md do publicador ou copie o caminho e abra o repositório. O PlugMCP lista a skill e não hospeda o arquivo.
O publicador o mantém em https://github.com/antfu/skills.
Claude, Cursor, Codex e Grok Build conseguem ler um SKILL.md que você adiciona a partir do repositório do publicador. O Grok Bot o instala quando você envia em um chat o link da pasta da skill no GitHub.