AgentSkillsCN

open-pr

提交拉取请求时，应以简洁明了的语义化标题搭配恰当的描述。无论是新建 PR、发起拉取请求，还是更新 PR 描述，亦或是已有 PR 但需检查并更新其描述时，均可采用此规范。

SKILL.md
--- frontmatter
name: open-pr
description: "Create or update a pull request with a terse semantic title and appropriate description. Use when creating a PR, opening a pull request, updating PR description, or when a PR already exists and the description should be checked and updated."

Open PR Skill

Create a new PR with a terse semantic title and body matching the project template, or—if a PR already exists for the branch—check and update the PR description (and title if needed).

When to Use

  • •Use when creating a new pull request after pushing a branch
  • •Use when a PR already exists and the description (or title) may be outdated

Prerequisites

  • •GitHub CLI (gh): Installed and authenticated (gh auth status)
  • •Pushed branch: Branch must be pushed before creating or updating the PR

PR Title

Same convention as commit messages: <type>(<scope>): <description>. Semantic, terse (under 50 chars), imperative. See CONTRIBUTING.md and AGENTS.md.

PR Body

Align with .github/pull_request_template.md: Description, Type of Change, Changes Made, Testing, Checklist, Related Issues. Fill from the branch's commits and diff.

Create Flow (No PR Yet)

  1. •Check for existing PR: gh pr view or gh pr list --head <branch>. If a PR exists, use Update flow instead
  2. •Compose terse semantic title and body from commits/diff
  3. •Create: gh pr create --title "..." --body "..." (or --body-file)

Update Flow (PR Exists)

  1. •Get current PR: gh pr view (title and body)
  2. •Compare with what the body/title should be given current commits/diff
  3. •If outdated: gh pr edit --body "..." and optionally --title "..."

Only update when description or title is inaccurate or incomplete.

Tooling

Prefer GitHub CLI (gh). If not available, instruct the user to install and authenticate.

Related Artifacts