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

create-pr-with-template

スター26

フォーク6

更新日2026年4月23日 14:16

Create a GitHub Pull Request with gh CLI and prefer repository PR templates automatically. Use this whenever the user asks to open/create a PR, especially when template compliance is needed. If multiple templates exist, ask the user which template to use.

インストール

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

Manusで実行

ソース

egermano

egermano/skills

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

ダウンロード

Manusで実行

Create PR with Template

Use this skill to create pull requests reliably using the GitHub CLI while respecting repository PR templates.

Outcomes

Create a PR with gh pr create.
Use a repository PR template when available.
Ask the user to choose only when multiple templates exist.
Return the final PR URL.

Safety and Scope

Use gh for all GitHub PR operations.
Do not force push.
Do not create or edit commits unless the user asked for that separately.
If the current branch has no remote tracking branch, push with -u before creating the PR.

Workflow

1) Inspect branch and diff context

Run:

git status --short
git branch --show-current
git rev-parse --abbrev-ref --symbolic-full-name @{u}
git log --oneline --decorate -n 20

If upstream is missing, note it and prepare to push current branch with git push -u origin <branch>.

Determine base branch:

Prefer repository default branch from GitHub when available.
Otherwise use main.

2) Discover PR templates

Search for templates in common locations:

.github/PULL_REQUEST_TEMPLATE.md
PULL_REQUEST_TEMPLATE.md
docs/PULL_REQUEST_TEMPLATE.md
.github/PULL_REQUEST_TEMPLATE/*.md

Behavior:

If no template exists: generate a clean body with a short summary.
If exactly one template exists: use it automatically.
If more than one template exists: ask the user which template to use and wait for the answer.

3) Build title and body

Gather PR content from branch commits and diff since base branch.

Guidelines:

Keep title concise and outcome-focused.
Keep body short and clear.
Preserve template section headers when template is used.
Fill placeholders with concrete changes from the branch.
Remove instructional comments from template in final body.

4) Ensure remote branch is ready

If branch is not pushed/upstream missing, push with upstream:

git push -u origin <branch>

If branch already tracks remote, push normally only if needed:

git push

5) Create the PR with gh

Use heredoc body for stable formatting:

gh pr create --base <base> --head <branch> --title "<title>" --body "$(cat <<'EOF'
<body>
EOF
)"

If the repository requires a specific template format, ensure body follows that template.

6) Return result

After successful creation, return only the essential outcome:

PR URL
Base and head branches
Template used (or none)

Multiple Template Prompt Contract

When multiple templates are found, ask one clear question listing options by number and file path:

Option 1: <path>
Option 2: <path>

Then continue only after user picks one.

Failure Handling

If gh is not authenticated, instruct user to run gh auth login and retry.
If PR already exists for head/base, return the existing PR URL.
If push fails due to permissions, report the exact failure and stop.

Response Contract

Final response must include the PR URL explicitly, for example:

PR created: https://github.com/org/repo/pull/123

このリポジトリの他の Skills

同じリポジトリ

split-commits-by-diff

egermano/skills

Split Git commits by diff hunks to create clean, scoped changes.

2026-06-0726

youtube-td

egermano/skills

YouTube Titles and Descriptions specialist for Azion tech videos. Creates optimized titles, descriptions, keywords, and timestamps to drive clicks and search rankings. Use this skill when the user asks for YouTube metadata, video titles, video descriptions, YouTube SEO, or shares a video concept that needs packaging for YouTube. Output is always in English.

2026-06-0226

cleanup-to-main

egermano/skills

Clean up local git branches that have been removed from the remote repository. Use when the user wants to tidy up their local git branches, remove stale branches, clean up after merging PRs, or mentions 'cleanup branches', 'remove old branches', 'prune local branches', 'git branch cleanup'. Safely handles uncommitted changes, preserves local-only branches, and provides a detailed report.

2026-05-2826

egermano/skills

Extreme Programming adapted for AI-human pair development. Use whenever the user wants to work in a structured, iterative way with their AI agent — mentions XP, extreme programming, pair programming, agile, YAGNI, simple design, continuous refactoring, or wants to plan before coding. Also use when the user wants to build features incrementally with tests, feedback loops, and clear role division between human and AI. This skill is the AI-era evolution of pair programming.

2026-05-2826

name	create-pr-with-template
description	Create a GitHub Pull Request with gh CLI and prefer repository PR templates automatically. Use this whenever the user asks to open/create a PR, especially when template compliance is needed. If multiple templates exist, ask the user which template to use.

Create PR with Template

Use this skill to create pull requests reliably using the GitHub CLI while respecting repository PR templates.

Outcomes

Create a PR with gh pr create.
Use a repository PR template when available.
Ask the user to choose only when multiple templates exist.
Return the final PR URL.

Safety and Scope

Use gh for all GitHub PR operations.
Do not force push.
Do not create or edit commits unless the user asked for that separately.
If the current branch has no remote tracking branch, push with -u before creating the PR.

Workflow

1) Inspect branch and diff context

Run:

git status --short
git branch --show-current
git rev-parse --abbrev-ref --symbolic-full-name @{u}
git log --oneline --decorate -n 20

If upstream is missing, note it and prepare to push current branch with git push -u origin <branch>.

Determine base branch:

Prefer repository default branch from GitHub when available.
Otherwise use main.

2) Discover PR templates

Search for templates in common locations:

.github/PULL_REQUEST_TEMPLATE.md
PULL_REQUEST_TEMPLATE.md
docs/PULL_REQUEST_TEMPLATE.md
.github/PULL_REQUEST_TEMPLATE/*.md

Behavior:

If no template exists: generate a clean body with a short summary.
If exactly one template exists: use it automatically.
If more than one template exists: ask the user which template to use and wait for the answer.

3) Build title and body

Gather PR content from branch commits and diff since base branch.

Guidelines:

Keep title concise and outcome-focused.
Keep body short and clear.
Preserve template section headers when template is used.
Fill placeholders with concrete changes from the branch.
Remove instructional comments from template in final body.

4) Ensure remote branch is ready

If branch is not pushed/upstream missing, push with upstream:

git push -u origin <branch>

If branch already tracks remote, push normally only if needed:

git push

5) Create the PR with gh

Use heredoc body for stable formatting:

gh pr create --base <base> --head <branch> --title "<title>" --body "$(cat <<'EOF'
<body>
EOF
)"

If the repository requires a specific template format, ensure body follows that template.

6) Return result

After successful creation, return only the essential outcome:

PR URL
Base and head branches
Template used (or none)

Multiple Template Prompt Contract

When multiple templates are found, ask one clear question listing options by number and file path:

Option 1: <path>
Option 2: <path>

Then continue only after user picks one.

Failure Handling

If gh is not authenticated, instruct user to run gh auth login and retry.
If PR already exists for head/base, return the existing PR URL.
If push fails due to permissions, report the exact failure and stop.

Response Contract

Final response must include the PR URL explicitly, for example:

PR created: https://github.com/org/repo/pull/123