pr-and-merge

スター7

フォーク0

更新日2026年3月7日 14:45

Commit current work, push, open a pull request, wait for CI to pass, then merge.

インストール

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

Manusで実行

ソース

mjwestcott

mjwestcott/dotfiles

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

ダウンロード

Manusで実行

関連職種SOC

SOC 職業分類に基づく

ソフトウェア開発者コンピュータ・数学職·SOC 15-1252

SKILL.md

readonly

name	pr-and-merge
description	Commit current work, push, open a pull request, wait for CI to pass, then merge.
user_invocable	true

Run the following steps:

Check the current branch. If on main or master, create a new feature branch first:
- Pick a short, descriptive branch name based on the recent changes (e.g. add-start-skill)
- Fetch latest main: git fetch origin main (or master)
- Create the branch from latest main: git checkout -b <branch> origin/main
- Cherry-pick or re-apply any uncommitted/staged work onto the new branch
Commit any uncommitted changes with a clear commit message.
Push the branch: git push -u origin HEAD
Open the PR with gh pr create, targeting main. Write a concise title and summary based on the changes.
Print the PR URL to the user.
Poll CI status with gh pr checks <pr-url> --watch until all checks complete.
- If checks pass, proceed to step 7.
- If checks fail, report the failures to the user and stop. Do not merge.
Merge the PR with gh pr merge <pr-url> --squash --delete-branch.
Switch back to main and pull: git checkout main && git pull
Confirm the merge to the user.

このリポジトリの他の Skills

同じリポジトリ

mjwestcott/dotfiles

Commit current work, push, and open a pull request against main.

2026-02-097

start

mjwestcott/dotfiles

Switch to main branch, pull latest changes, and optionally begin work on a task.

2026-02-097

validate

mjwestcott/dotfiles

Manually test your work against the locally running app by making real API or HTTP requests.

2026-02-097

scaffold

mjwestcott/dotfiles

Scaffold a new project from the fullstack or Rust CLI boilerplate. Use when starting a new codebase.

2026-01-187

coverage

mjwestcott/dotfiles

Comprehensive analysis of testing strategy and coverage across the codebase. Evaluates all test types and identifies gaps.

2026-01-177

tests

mjwestcott/dotfiles

Reviews test coverage and testing strategy for recent code changes. Use before creating PRs to ensure changes are well-tested.

2026-01-177

name	pr-and-merge
description	Commit current work, push, open a pull request, wait for CI to pass, then merge.
user_invocable	true

Run the following steps:

Check the current branch. If on main or master, create a new feature branch first:
- Pick a short, descriptive branch name based on the recent changes (e.g. add-start-skill)
- Fetch latest main: git fetch origin main (or master)
- Create the branch from latest main: git checkout -b <branch> origin/main
- Cherry-pick or re-apply any uncommitted/staged work onto the new branch
Commit any uncommitted changes with a clear commit message.
Push the branch: git push -u origin HEAD
Open the PR with gh pr create, targeting main. Write a concise title and summary based on the changes.
Print the PR URL to the user.
Poll CI status with gh pr checks <pr-url> --watch until all checks complete.
- If checks pass, proceed to step 7.
- If checks fail, report the failures to the user and stop. Do not merge.
Merge the PR with gh pr merge <pr-url> --squash --delete-branch.
Switch back to main and pull: git checkout main && git pull
Confirm the merge to the user.