AgentSkillsCN

create-pr

通过 gh CLI 创建清晰且可供审查的拉取请求。从提交记录与差异中提炼上下文，遵循仓库模板规范，安全推送，并附上合并建议的 PR URL。

SKILL.md
--- frontmatter
name: create-pr
description: "Create a clear, review-ready pull request with gh CLI. Gather context from commits and diff, follow repository templates, push safely, and return the PR URL with merge guidance."

Create Pull Request

Goal

Open a high-quality PR that is easy to review and safe to merge:

  • •includes only intended changes
  • •uses a clear title and useful body
  • •follows repo PR template when present
  • •reports final PR status and next actions

Inputs

  • •base_branch (optional, default: repo default branch)
  • •is_draft (true/false, default: false)
  • •title_hint (optional)
  • •extra_context (optional: issue links, rollout notes, risks)

Safety rules

  1. •Never create a PR from main/master directly.
  2. •Never include unrelated unstaged/uncommitted changes.
  3. •Do not rewrite branch history unless explicitly requested.
  4. •If history rewrite is required, use --force-with-lease only.
  5. •If a PR already exists for the branch, do not create a duplicate.

Workflow

  1. •

    Check prerequisites

    • •gh auth status
    • •git status --short --branch
    • •git branch --show-current
  2. •

    Determine base branch

    • •Prefer user input.
    • •Otherwise use repo default branch:
      • •gh repo view --json defaultBranchRef -q .defaultBranchRef.name
  3. •

    Review branch content

    • •git log --oneline origin/<base_branch>..HEAD
    • •git diff --stat origin/<base_branch>...HEAD
    • •Confirm scope is coherent and PR-ready.
  4. •

    Ensure branch is pushed

    • •If no upstream: git push -u origin HEAD
    • •Otherwise: git push
  5. •

    Build PR content

    • •Title: concise, outcome-focused; Conventional Commit style preferred.
    • •Body:
      • •If .github/pull_request_template.md (or equivalent) exists, follow it exactly.
      • •Otherwise include: context, summary, testing, risk/rollback, related issue.
  6. •

    Create or reuse PR

    • •Check existing PR first:
      • •gh pr view --json url,number,state 2>/dev/null
    • •If existing PR found, return it and summarize status.
    • •If no PR exists, create it:
bash
gh pr create --title "<title>" --body "<body>" --base <base_branch>

For draft PR:

bash
gh pr create --title "<title>" --body "<body>" --base <base_branch> --draft
  1. •Post-create checks
    • •gh pr view --json url,number,title,state,mergeStateStatus,reviewDecision
    • •Report CI/review state and what remains before merge.

Validation

  • •Prefer smallest relevant checks before PR creation (lint/unit/targeted tests).
  • •Include test commands and concise outcomes in the PR body.
  • •If checks were not run, state why and call it out explicitly.

Output format

Return:

  • •PR number + URL
  • •base/head branches
  • •draft or ready status
  • •merge/check state
  • •test summary (commands + results)
  • •recommendation: ready for review, wait for CI, or needs follow-up

Error handling

  • •If working tree is dirty, ask to commit or stash first.
  • •If no commits ahead of base, report no PR needed.
  • •If gh auth fails, instruct to run gh auth login.
  • •If creation fails due to permissions, report exact error and next step.