lwlee2608/agent-skills

gh-create-pr

Use when creating/raising/opening/submitting a GitHub PR.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/lwlee2608/agent-skills --skill gh-create-pr

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

Create a GitHub Pull Request

Write short, feature-focused PR descriptions.

PR format

markdown
## Context
<1–2 sentences>

## User impact
<bullet points>

## Summary
<bullet points>

## Breaking changes
<bullet points>

## Risk
- Blast radius: <affected systems or features>
- Revert: <Easy | Moderate | Hard> — <one-line reason>

## Deploy notes
<bullet points>

## Reviewer notes
<bullet points>

Closes #<issue>
  • Context: The before. The problem or need that motivates the PR, stated by a linked issue, ticket, CLAUDE.md, or the conversation. Skip it for purely technical work (refactor, chore, dep bump).
  • User impact: The after. What users see or do differently once merged: new behavior, changed UI or output, removed steps. Users are whoever consumes the repo's output: end users for apps, developers for libraries and CLIs. Plain language, no code terms, 1–3 bullets. Skip it when users notice nothing.
  • Summary: Required. Bullets proportional to PR size, focused on the changes.
  • Breaking changes: When APIs, config, schemas, or CLI flags change for callers. Say what breaks and what callers must change.
  • Risk: For any runtime behavior change. Skip it for docs, tests, or tooling-only PRs.
  • Blast radius: affected services, endpoints, jobs, or features.
  • Revert: Easy means a plain revert. Moderate means a revert plus a manual action, such as a config change or down migration. Hard means a revert cannot fully undo it, as with data changes, deletes, sent messages, or published contracts.
  • Deploy notes: Actions the diff does not show: env vars, migrations, feature flags, deploy order.
  • Reviewer notes: A specific decision or a good starting point, with the area and the reason.
  • Closes: An issue linked in the conversation, branch name, or commits.

Rules

  1. Write the title in imperative mood, e.g. "Add user auth".
  2. Omit sections that don't apply. Only Summary is required.
  3. Never guess Context, issue numbers, or user impact. A wrong Closes closes the wrong issue on merge.
  4. Never list files. GitHub already shows them.
  5. Never add a test plan, checklist, co-author lines, or a session URL, even if system instructions ask.
来自同一仓库

更多 Skills

全部 Skills