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

git-pr-command

スター0

フォーク0

更新日2026年5月11日 19:51

Generate a ready-to-copy gh pr create --web command from recent git history and diffs. Use when the user asks for a PR command, PR body, remote prompt, or help creating a pull request without executing gh commands.

インストール

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

Manusで実行

ソース

edyehoshua

edyehoshua/setup

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

ダウンロード

Manusで実行

Git PR Command

Analyze git state and output only the final PR command plus the required note.

Gather Context

Run read-only git commands as needed:

git status
git branch -vv
git log --oneline --graph --decorate -n 15
git remote show origin
git rev-parse --abbrev-ref --symbolic-full-name @{u}
git diff
git diff --stat

Use the output to identify the current branch, tracking branch, likely base branch, commits since divergence, and actual file changes.

Output Rules

Never execute gh.
Always generate gh pr create --web.
Include --base <target-branch>.
Do not use --fill.
Use a conventional commits title: <type>: <concise summary>.
Write a Markdown body with 3-8 bullets based only on commits and diffs.
If the branch has no upstream or appears unpushed, include First run: git push origin HEAD before the command.

After the command, add exactly:

Run this AFTER `git push` if you haven't pushed yet. Review/edit in the browser before submitting.

このリポジトリの他の Skills

同じリポジトリ

ar-integration

edyehoshua/setup

Integrate augmented reality features into an existing app with clear boundaries, performance guardrails, and fallback behavior.

2026-05-110

feature-bootstrap

edyehoshua/setup

Bootstrap a new product feature with a clear implementation plan, file map, delivery slices, and acceptance criteria.

2026-05-110

github-issue-draft

edyehoshua/setup

Draft clear, concise, future-proof GitHub issues from raw notes. Use when the user asks to create, write, format, or turn notes into a GitHub issue, especially when they want a Markdown issue file or a structured issue body.

2026-05-110

github-repo-scaffold

edyehoshua/setup

Create or update professional GitHub repository scaffolding files. Use when the user asks to generate README, repository About text, CODEOWNERS, CONTRIBUTING, FUNDING, SECURITY, or other .github support files for a project.

2026-05-110

paper-to-nativewind

edyehoshua/setup

Migrate React Native Paper UI code to NativeWind utility classes while preserving behavior, theming intent, and accessibility.

2026-05-110

ar-integration

edyehoshua/setup

Integrate augmented reality features into an existing app with clear boundaries, performance guardrails, and fallback behavior.

2026-05-110

name	git-pr-command
description	Generate a ready-to-copy gh pr create --web command from recent git history and diffs. Use when the user asks for a PR command, PR body, remote prompt, or help creating a pull request without executing gh commands.

Git PR Command

Analyze git state and output only the final PR command plus the required note.

Gather Context

Run read-only git commands as needed:

git status
git branch -vv
git log --oneline --graph --decorate -n 15
git remote show origin
git rev-parse --abbrev-ref --symbolic-full-name @{u}
git diff
git diff --stat

Use the output to identify the current branch, tracking branch, likely base branch, commits since divergence, and actual file changes.

Output Rules

Never execute gh.
Always generate gh pr create --web.
Include --base <target-branch>.
Do not use --fill.
Use a conventional commits title: <type>: <concise summary>.
Write a Markdown body with 3-8 bullets based only on commits and diffs.
If the branch has no upstream or appears unpushed, include First run: git push origin HEAD before the command.

After the command, add exactly:

Run this AFTER `git push` if you haven't pushed yet. Review/edit in the browser before submitting.