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

pr

スター2

フォーク0

更新日2026年6月22日 02:43

Commit, push, and open a pull request for the current change. Use when the user says open a PR, ship this, commit and push, or as the PR creation step of /ship. Requires verification evidence in the PR body.

インストール

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

Manusで実行

ソース

leighstillard

leighstillard/coach-ship-skills

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

ダウンロード

Manusで実行

PR

Goal

A clean branch is pushed and a PR exists with enough evidence for a reviewer to understand what changed, why, how it was verified, and what risk remains.

Step 1: Pre-flight

Run git status --short --untracked-files=all and inspect git diff / staged diff.
Confirm no secrets, .env, debug prints, unrelated files, generated junk, or large binaries are included.
Identify the default branch (gh repo view --json defaultBranchRef or git symbolic-ref refs/remotes/origin/HEAD).
Do not commit on the default branch. Create a short kebab-case branch if needed.
If the branch is stale, rebase/merge according to repo convention before opening the PR.

Step 2: Commit

Stage deliberately by path. Use git add -A only after every untracked path is accounted for.
Match commit convention from recent history.
Summary line: imperative, ≤72 chars, states what changed and why.
Keep one logical change per commit unless repo convention prefers squash-only noise-free branches.

Step 3: PR body

Check for .github/PULL_REQUEST_TEMPLATE* and honor it. Include, at minimum:

What — concise behaviour/change summary.
Why — user issue/ticket/context.
How verified — paste the verification evidence: commands and representative output. Tests pass alone is insufficient.
Review/design — independent review status and design screenshots/output when applicable.
Risk / rollback — likely failure modes and how to revert/disable.

Step 4: Push/open

Run:

git push -u origin <branch>
gh pr create --title "<summary>" --body "<body>"

Then output the PR URL.

Gotchas

If gh auth status fails, stop and ask for auth; do not improvise credentials.
Do not force-push over review activity without explicit instruction.
If diff is very large, mention split risk before opening unless the user explicitly asked for one PR.
CI config changes must be called out in the PR body.

このリポジトリの他の Skills

同じリポジトリ

babysit

leighstillard/coach-ship-skills

Shepherd an open PR to merge. Watches CI, fixes failures, addresses review comments, resolves conflicts, and enables/executes merge when green. Use after opening a PR, when the user says babysit/watch/get this merged, or as the final step of /ship.

2026-06-222

design-check

leighstillard/coach-ship-skills

Visual and UX review for user-visible changes: frontend components, HTML/CSS, templates, dashboards, rendered docs, emails, and CLI output formatting. Use as part of /ship when a diff touches UI/human-facing output. If nothing user-visible changed, explicitly mark not applicable and stop.

2026-06-222

ship

leighstillard/coach-ship-skills

Take a finished local change to a merged PR through non-negotiable release gates. Use when the user says ship it, /ship, get this merged, release this, or when /coach has a READY local diff. Enforces simplify, verify, design applicability, PR evidence, independent review, CI, and merge babysitting while preserving Anthropic budget where safe.

2026-06-222

simplify

leighstillard/coach-ship-skills

Simplify a completed diff before it ships. Use before /ship, after a feature works, or when a change feels over-engineered. Removes unnecessary abstraction, scope creep, dead code introduced by the diff, and confusing structure without changing behaviour.

2026-06-222

verify

leighstillard/coach-ship-skills

Prove a change actually works before it ships. Use whenever a change is done, after implementing a feature/fix, before opening a PR, or when the user says verify/check this works/is this actually working. Tests passing is not sufficient; this skill requires real entry-point evidence.

2026-06-222

Goal

A clean branch is pushed and a PR exists with enough evidence for a reviewer to understand what changed, why, how it was verified, and what risk remains.

Step 1: Pre-flight

Run git status --short --untracked-files=all and inspect git diff / staged diff.

Confirm no secrets, .env, debug prints, unrelated files, generated junk, or large binaries are included.

Identify the default branch (gh repo view --json defaultBranchRef or git symbolic-ref refs/remotes/origin/HEAD).

Do not commit on the default branch. Create a short kebab-case branch if needed.

If the branch is stale, rebase/merge according to repo convention before opening the PR.

Step 2: Commit

Stage deliberately by path. Use git add -A only after every untracked path is accounted for.

Match commit convention from recent history.

Summary line: imperative, ≤72 chars, states what changed and why.

Keep one logical change per commit unless repo convention prefers squash-only noise-free branches.

Step 3: PR body

Check for .github/PULL_REQUEST_TEMPLATE* and honor it. Include, at minimum:

What — concise behaviour/change summary.

Why — user issue/ticket/context.

How verified — paste the verification evidence: commands and representative output. Tests pass alone is insufficient.

Review/design — independent review status and design screenshots/output when applicable.

Risk / rollback — likely failure modes and how to revert/disable.

Step 4: Push/open

Run:

git push -u origin <branch> gh pr create --title "<summary>" --body "<body>"

Then output the PR URL.

Gotchas

If gh auth status fails, stop and ask for auth; do not improvise credentials.

Do not force-push over review activity without explicit instruction.

If diff is very large, mention split risk before opening unless the user explicitly asked for one PR.

CI config changes must be called out in the PR body.

name	pr
description	Commit, push, and open a pull request for the current change. Use when the user says open a PR, ship this, commit and push, or as the PR creation step of /ship. Requires verification evidence in the PR body.