ワンクリックでManusで任意のスキルを実行

create-pr

スター0

フォーク0

更新日2026年2月2日 22:01

Create GitHub pull requests with the gh CLI using a conventional-commit title that matches recent commits and a description derived from the diff or a design doc. Use when asked to open a PR, draft a PR, or generate PR titles/bodies from git changes in this repo.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

mplemay

mplemay/brussels

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Create Pr

Overview

Create a PR with gh pr create using a conventional-commit title aligned with the latest commit(s) and a body derived from the design doc or diff.

Workflow

1) Collect change context

Confirm a clean working tree or commit any staged work.
Gather high-signal context:
- git status -sb
- git log -1 --pretty=%s for the most recent conventional-commit subject.
- git diff --stat and git diff for change scope and details.
- If the repo has a main branch, also compare against it to scope the PR:
  - git diff --stat main...HEAD and git diff main...HEAD

2) Prefer design docs when present

If any design document is part of the change set, base the PR description primarily on it.
Locate design docs in diffs or the design/ directory (e.g., git diff --name-only | rg '^design/').
If no design doc is present, base the description on the code changes and tests from the diff.

3) Build the PR title (conventional commit)

Use the most recent conventional commit subject as the PR title.
If multiple commits are present, pick the dominant type/scope and keep the same naming style as the commits.
Keep it a single-line conventional-commit subject, e.g. feat(parser): add schema validation.

4) Draft the PR body (design doc or diff)

Use a short template:
- Summary: 2–5 bullets describing what changed and why.
- Testing: list tests run or Not run (reason).
- Design: link or reference the design doc if present, otherwise omit.

5) Create the PR with gh

Prefer non-interactive creation to ensure title/body accuracy:
- gh pr create --title "<conventional-subject>" --body "<body text>"
Use flags as needed:
- --base / --head to control branches.
- --draft for draft PRs.
- --assignee, --reviewer, --label if requested.

6) Validate output

Confirm the created PR URL and skim the rendered description for correctness.

このリポジトリの他の Skills

同じリポジトリ

commit-and-push

mplemay/brussels

Run the repo's finalize workflow (uv pytest, pre-commit with per-hook fixes, conventional commit, git push). Use when asked to run tests/lint, fix hook failures, commit changes, or push updates.

2026-02-020

design-doc

mplemay/brussels

Create a detailed design document in a repo's design/ folder using its template and conventions. Use when the user asks for a design doc, design document, or "$design-doc" that should be numbered (NNN-...), formatted like design/000-design-template.md and design/000-design-example.md, and focused on architecture, workflows, APIs, dependencies, and tests (not implementation).

2026-02-020

name	create-pr
description	Create GitHub pull requests with the gh CLI using a conventional-commit title that matches recent commits and a description derived from the diff or a design doc. Use when asked to open a PR, draft a PR, or generate PR titles/bodies from git changes in this repo.

Create Pr

Overview

Create a PR with gh pr create using a conventional-commit title aligned with the latest commit(s) and a body derived from the design doc or diff.

Workflow

1) Collect change context

Confirm a clean working tree or commit any staged work.
Gather high-signal context:
- git status -sb
- git log -1 --pretty=%s for the most recent conventional-commit subject.
- git diff --stat and git diff for change scope and details.
- If the repo has a main branch, also compare against it to scope the PR:
  - git diff --stat main...HEAD and git diff main...HEAD

2) Prefer design docs when present

If any design document is part of the change set, base the PR description primarily on it.
Locate design docs in diffs or the design/ directory (e.g., git diff --name-only | rg '^design/').
If no design doc is present, base the description on the code changes and tests from the diff.

3) Build the PR title (conventional commit)

Use the most recent conventional commit subject as the PR title.
If multiple commits are present, pick the dominant type/scope and keep the same naming style as the commits.
Keep it a single-line conventional-commit subject, e.g. feat(parser): add schema validation.

4) Draft the PR body (design doc or diff)

Use a short template:
- Summary: 2–5 bullets describing what changed and why.
- Testing: list tests run or Not run (reason).
- Design: link or reference the design doc if present, otherwise omit.

5) Create the PR with gh

Prefer non-interactive creation to ensure title/body accuracy:
- gh pr create --title "<conventional-subject>" --body "<body text>"
Use flags as needed:
- --base / --head to control branches.
- --draft for draft PRs.
- --assignee, --reviewer, --label if requested.

6) Validate output

Confirm the created PR URL and skim the rendered description for correctness.