AgentSkillsCN

gh-pr-create

通过 gh 工具，依据仓库中的 PULL_REQUEST_TEMPLATE.md 文件创建 GitHub Pull Request。当用户提出“创建 PR”、“推送并打开 PR”、“提及 PR 模板”或希望补充背景信息与 QA 部分时，此技能将自动触发。

SKILL.md
--- frontmatter
name: gh-pr-create
description: Create GitHub PRs via gh using the repository PULL_REQUEST_TEMPLATE.md. Trigger when the user says to create a PR, asks to push and open a PR, mentions PR templates, or wants background/QA sections filled.

GH PR Create

Use this skill when asked to create a PR using gh pr create and the repo’s PR template.

Workflow

  1. •

    Check status

    • •!git status -sb
    • •If nothing to push, ask user whether to proceed.
    • •Confirm base branch and compare commits against base:
      • •!git rev-parse --abbrev-ref HEAD
      • •!git log --oneline <base>..HEAD
  2. •

    Confirm template

    • •Read .github/PULL_REQUEST_TEMPLATE.md to align sections.
    • •If template missing, proceed with a minimal body.
  3. •

    Prepare PR body

    • •Use the base-branch diff and commit list to propose 背景・課題・Issue yourself, then ask the user to confirm or adjust.
    • •Write background as concise lines without bullets.
    • •If the repo is balus-co-ltd/spwn (or has the same template), follow the template: keep pr_agent:summary, remove resolve # when instructed, and place the userの背景 in 背景・課題・Issue.
    • •Otherwise, write the background as concise sentences (not bullet-heavy) and keep the body minimal.
    • •For 実装詳細・変更点概要, leave the template placeholder unless user explicitly asks to write it.
    • •For QA, default to:
      • •E2E: 未実施
      • •Manual: 1. 未実施
    • •Keep sections and wording consistent with the template when one exists.
  4. •

    Decide optional steps

    • •Push branch only if not already pushed.
    • •Create PR only if not already exists.
  5. •

    Create PR

    • •Use gh pr create --base <base> --head <branch> --title <title> --body <body>.
    • •Base defaults to the user’s target branch (e.g., develop). Ask if unclear.
    • •When building --body, pass real newlines (not \n escapes). Use a heredoc / multiline string.

Guardrails

  • •PR title: Use a conventional-commit-like prefix and a short English summary in lowercase. Examples:
    • •ci: align pipeline cache keys
    • •chore: tidy workspace scripts
    • •docs: clarify release steps
    • •feat: add admin export endpoint
    • •fix: prevent duplicate checkout Naming rules:
    • •Present tense
    • •Under 50 characters
    • •No trailing period
    • •Omit scope unless it adds clarity
  • •Do not overwrite template sections beyond what the user requested.
  • •If the user wants background only, keep other sections untouched.
  • •If the user says “auto-generate details,” keep pr_agent:summary and do not edit it.
  • •Keep the PR body concise; avoid extra sections.

Prompts to ask when unclear

  • •“ベースブランチは何ですか？（例: develop）”
  • •“ベースとの差分/コミット一覧を見ました。背景・課題・Issue をあなたの言葉で教えてください。”
  • •“PRのベースブランチは develop で良いですか？”
  • •“resolve # を消して良いですか？”
  • •“背景・課題に入れる箇条書きを教えてください。”

Note on newlines in PR body

  • •If the PR body is passed as a single-line string containing \\n, zsh will not expand it, and gh may truncate the body.
  • •Prefer a heredoc / multiline string so real newlines are passed.