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

create-pr

スター6

フォーク12

更新日2026年6月27日 06:31

Create a GitHub pull request from the current branch. Use when the user asks to create a PR, open a pull request, or submit a PR for review. Assumes branch is pushed. Auto-generates title and description from commit history.

インストール

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

Manusで実行

ソース

404-PF

404-PF/New-Tab

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

ダウンロード

Manusで実行

Create Pull Request

When to Use

User asks to "create a PR", "open a pull request", or "submit for review"
User wants to submit changes for team review
After completing work on a feature branch

Prerequisites

Current branch must have at least one commit ahead of the base branch
Branch will be auto-pushed to remote if not already pushed

Procedure

1. Determine Branch Context

Identify the current branch name
Identify the base branch (default: main, or use the argument if provided)
Verify there are commits ahead of the base branch
If branch has no upstream or has unpushed commits, push automatically (git push -u origin <branch>)

2. Analyze Commits

Run git log --oneline base..current to get all commits on the feature branch
Group commits by type (feat, fix, refactor, docs, test, chore, etc.)
Identify the primary change/feature being introduced

3. Generate PR Metadata

Title (max 72 characters):

Use the first line of the most significant commit, or synthesize from commit grouping
Follow Conventional Commits format when commits use it: type(scope): description

Description body (Markdown):

## Summary
[1-2 sentence description of what this PR accomplishes]

## Changes
- **feat**: [list of feature commits]
- **fix**: [list of bug fix commits]
- **refactor**: [list of refactors]
- [other categories as needed]

## Testing
[How to test these changes, if evident from commits or code]

## Related
[Closes #123, Fixes #456 if commit messages reference issues]

4. Ask User for Confirmation

Before creating the PR, present:

The generated title
The generated description
Ask: Draft or Ready for review?

5. Create the Pull Request

Prefer GitHub MCP tools (mcp_github_mcp_se_create_pull_request) to create the PR. If MCP tools are unavailable or fail, fall back to gh CLI in the terminal:

gh pr create --base <base> --head <head> --title "<title>" --body "<body>"

Set the following:

title → generated title
body → generated description
head → current branch
base → target branch
draft → based on user preference

6. Report Result

Display the created PR URL
Suggest next steps (e.g., request reviewers, add labels)

Example Usage

User: "create a PR" → Skill detects current branch feat/user-auth, base main → Analyzes 5 commits, generates title and description → Presents to user for review → Creates PR when confirmed

User: "create a PR targeting develop" → Uses develop as the base branch instead of main

Notes

If commits are not conventional format, synthesize description from commit diffs
For single-commit PRs, use the commit message directly
Always verify remote tracking branch exists or offer to push

このリポジトリの他の Skills

同じリポジトリ

checkout-branch

404-PF/New-Tab

Create and switch to a new branch. Accepts a branch name or GitHub issue number. Derives branch name from issue title when an issue number is given. USE FOR: starting new work, branching from an issue, creating feature/bugfix branches. DO NOT USE FOR: committing, pushing, or managing PRs.

2026-06-276

commit

404-PF/New-Tab

**WORKFLOW SKILL** — Stage changes, write clear commit messages, and commit following best practices. USE FOR: committing code changes; writing conventional commit messages; staging files before commits; amending previous commits; creating atomic commits; generating commit messages from diffs. DO NOT USE FOR: pushing to remote (use git push); resolving merge conflicts; branching or rebasing.

2026-06-276

create-issue

404-PF/New-Tab

Create a GitHub issue with proper structure and metadata. Use when the user asks to create an issue, open a ticket, report a bug, or request a feature. Supports labels, assignees, milestones, and templates.

2026-06-276

create-release

404-PF/New-Tab

Create GitHub releases with automated versioning and changelog generation. Use for: publishing releases, creating tags, generating release notes, version bumping, semantic versioning.

2026-06-276

patch-findings

404-PF/New-Tab

Generate fix patches from pre-identified findings. Use when: generating code fixes from PR review comments, producing patches from scan results, translating described problems into code changes. DO NOT USE FOR: resolving GitHub issues (use resolve-issue); creating PRs (use create-pr); managing branches.

2026-06-276

resolve-issue

404-PF/New-Tab

**WORKFLOW SKILL** — Systematically resolve GitHub issues from assignment through PR creation. USE FOR: working on assigned issues; following structured debugging workflows; implementing feature requests; fixing bugs reported in issues; creating focused PRs linked to issues. DO NOT USE FOR: creating new issues (use create-issue); reviewing PRs (use review-pr); general coding tasks without an issue context.

2026-06-276

name	create-pr
description	Create a GitHub pull request from the current branch. Use when the user asks to create a PR, open a pull request, or submit a PR for review. Assumes branch is pushed. Auto-generates title and description from commit history.
user-invocable	true
argument-hint	Optional: base branch name (defaults to main)

Create Pull Request

When to Use

User asks to "create a PR", "open a pull request", or "submit for review"
User wants to submit changes for team review
After completing work on a feature branch

Prerequisites

Current branch must have at least one commit ahead of the base branch
Branch will be auto-pushed to remote if not already pushed

Procedure

1. Determine Branch Context

Identify the current branch name
Identify the base branch (default: main, or use the argument if provided)
Verify there are commits ahead of the base branch
If branch has no upstream or has unpushed commits, push automatically (git push -u origin <branch>)

2. Analyze Commits

Run git log --oneline base..current to get all commits on the feature branch
Group commits by type (feat, fix, refactor, docs, test, chore, etc.)
Identify the primary change/feature being introduced

3. Generate PR Metadata

Title (max 72 characters):

Use the first line of the most significant commit, or synthesize from commit grouping
Follow Conventional Commits format when commits use it: type(scope): description

Description body (Markdown):

## Summary
[1-2 sentence description of what this PR accomplishes]

## Changes
- **feat**: [list of feature commits]
- **fix**: [list of bug fix commits]
- **refactor**: [list of refactors]
- [other categories as needed]

## Testing
[How to test these changes, if evident from commits or code]

## Related
[Closes #123, Fixes #456 if commit messages reference issues]

4. Ask User for Confirmation

Before creating the PR, present:

The generated title
The generated description
Ask: Draft or Ready for review?

5. Create the Pull Request

Prefer GitHub MCP tools (mcp_github_mcp_se_create_pull_request) to create the PR. If MCP tools are unavailable or fail, fall back to gh CLI in the terminal:

gh pr create --base <base> --head <head> --title "<title>" --body "<body>"

Set the following:

title → generated title
body → generated description
head → current branch
base → target branch
draft → based on user preference

6. Report Result

Display the created PR URL
Suggest next steps (e.g., request reviewers, add labels)

Example Usage

User: "create a PR targeting develop" → Uses develop as the base branch instead of main

Notes

If commits are not conventional format, synthesize description from commit diffs
For single-commit PRs, use the commit message directly
Always verify remote tracking branch exists or offer to push