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