pr-creator
Creates or updates GitHub PRs with house-style titles and bodies, issue linking, repository templates, and draft state. Use when asked to "create a PR", "rewrite the PR description", or "polish this PR". For code fixes use tidy; for CI and review threads use pr-babysitter; for npm releases use autoship.
mblode · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add mblode/agent-skills --skill pr-creator技能说明
name: pr-creator description: Creates or updates GitHub PRs with house-style titles and bodies, issue linking, repository templates, and draft state. Use when asked to "create a PR", "rewrite the PR description", or "polish this PR". For code fixes use tidy; for CI and review threads use pr-babysitter; for npm releases use autoship. compatibility: Requires Git and authenticated GitHub access. The documented command workflow uses GitHub CLI.
pr-creator
Write PR descriptions like a developer posting in Slack, not an AI summarizing a diff.
- IS: creating or updating a GitHub PR's title, body, draft state, and reviewers, plus the commit restructuring and review path that make a large diff readable.
- IS NOT: changing the code in the diff (use
tidy), reviewing it for bugs (usepr-reviewer), watching CI and review comments after the PR exists (usepr-babysitter), or cutting npm releases (useautoship).
Reference Files
| File | Read When |
|---|---|
references/pr-polish.md | Commits contain fixup, WIP, or "address review" noise, the diff exceeds 500 lines, or the user asks to polish, restructure, squash, or split the PR |
Workflow
Copy this checklist to track progress:
PR creation progress:
- [ ] Inspect the current branch and diff against the existing PR base, or the discovered default branch merge-base
- [ ] Existing PR? gh pr view --json url,state,isDraft (state OPEN means edit, not create)
- [ ] Linear ID from branch, commits, prompt, or issue link; no ID means no prefix
- [ ] Noisy commits or a >500-line diff? references/pr-polish.md, before pushing
- [ ] PR template present? Read it (paths under Templates)
- [ ] Draft title and body against Rules and Anti-patterns
- [ ] git push -u origin HEAD
- [ ] gh pr create (or gh pr edit); then gh pr view --json url,title and return the URL
Do not ask the user to approve the description first; the point is speed. They can ask for a rewrite and you run gh pr edit.
Rules
- Title. With a Linear ID:
ABC-123: Add auth flow. Without one:Add auth flow. Under 60 characters, no trailing period. If the repo lints PR titles (asemantic-pull-requestor commitlint workflow under.github/workflows/), use its shape and put the ID at the end:feat: add auth flow (ABC-123). Linear links on the ID wherever it sits in the title. - Body. One short paragraph: what changed and why it matters. Length follows the change; a one-line body is fine for a one-line fix.
- No fake why. If the reason is not in the prompt, the Linear issue, the branch, the commits, or the diff, leave it out rather than inventing one.
- Risk only when real. One
Risk:line for migrations, billing, auth, permissions, irreversible writes, wide blast radius, or a subtle behavior change. Otherwise nothing. - Testing only if real. Say what you ran only if you ran it. Never a
Test plansection, never checkboxes. - Partial work. If this PR does not finish the Linear issue, keep the ID out of the title and write
Part of ABC-123in the body. Linear's default automation moves a linked issue to Done when the PR merges; the non-closing magic word links without closing. - Draft and reviewers only when asked.
--draftfor "draft" or "WIP";gh pr readypromotes it later,gh pr ready --undodemotes.--reviewer alice,org/teamonly for people the user named; CODEOWNERS already requests owners. - Stop after the useful content. The harness's
attributionsetting owns the PR footer (Generated with Claude Code, session link). Never hand-write one, and never strip one the harness or a repo policy appends. Everything above the footer is this skill's; its one-paragraph body replaces the harness's defaultSummaryandTest plansections.
Anti-patterns: never write these
- Openers that narrate the artifact: "This PR implements...", "This change ensures...", "This commit introduces..."
- Changelog verbs with no reason attached: "Refactored X to improve Y", "Updated Z to handle...", "Added comprehensive test coverage for..."
- Lines that start with a filename or path; the diff already lists the files
- A
Test plansection with checkboxes - A bullet list that restates the diff
Examples
Feature (ABC-123 is the real Linear ID)
Title: ABC-123: Add auth flow with session management
Adds the auth flow needed for session-based login, including refresh, timeout handling, and a small error boundary for auth failures.
Bugfix (real risk, real testing)
Title: PAY-482: Dedupe Stripe webhook retries
Stripe retries webhooks on timeout and our handler wasn't idempotent, so retried events created duplicate invoices. Now we record processed event IDs and skip repeats. Tested by replaying a captured retry sequence locally.
Risk: touches the billing write path.
Chore (no Linear ID, no why beyond the diff)
Title: Bump eslint to 9 and fix the new no-unused-vars hits
Bumps eslint to 9. The only code change is removing three unused imports it now flags.
The first two carry the real why from the commits and stop. Risk: earns its line in the second because the diff touches billing writes; the testing sentence is there only because a replay actually ran. The third has no deeper why, so it does not pretend to.
Templates
GitHub reads the first match of pull_request_template.md (case-insensitive) in .github/, the repo root, or docs/, or a PULL_REQUEST_TEMPLATE/ directory in any of those for multiple templates. gh pr create --body skips the template entirely, so when one exists, read it and write the body in its shape: keep its headings, answer each in a sentence or two, and put the one-paragraph description under the first heading. Add nothing the template does not ask for.
Creating the PR
Write the exact body to a temporary file with the file tool, then pass its path through --body-file. The examples use `/tmp/pr-body.md