メニュー
PR merge strategy, branch cleanup and post-merge hygiene for any pull request. Use when merging a PR, cleaning up after a merge or deciding how to land changes. See github-pr-stack-convention when PRs depend on other PRs.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Drive a real browser with the browser_go, browser_see, browser_do and browser_check tools: navigate, read the page as an accessibility outline, query the DOM across frames and shadow roots, inspect one element's box and cascade, run expressions, press keys and gestures, wait for conditions, read console and network telemetry, emulate devices, shape the network, take screenshots, and form verdicts about accessibility, layout, design drift, visual diffs and performance. Use when asked to "open a page", "look at this site", "click the button", "what does the page say", "why is this element red", "check the console", "what requests did it make", "test it on mobile", "is this accessible", "did the layout break", "what changed visually", or any request that involves looking at or operating a web page.
How to audit a web page for accessibility with browser_check and browser_see: the keyboard walk, the axe and structural rule sets, reading order, live region announcements, contrast and target size. Covers what the tools decide, what they deliberately refuse to decide, and how to report findings without overstating them. Use when asked "is this accessible", "check accessibility", "run an a11y audit", "will a screen reader work", "can you use this with a keyboard", "check the contrast", "is this WCAG compliant", or when reviewing a change that touches markup, focus, colour or interaction.
Output contract for round-1 council reviewer subagents in pr-workflow. The JSON shape of findings, location kinds, thread-relation fields, and the verify_output self-check protocol. Loaded into each reviewer subagent via --skill.
Output contract for round-3 critique reviewer subagents in pr-workflow. The JSON shape of critique entries, position vocabulary, rationale requirements, and the verify_output self-check protocol. Loaded into each critique reviewer subagent via --skill.
Output contract for round-2 judge subagents in pr-workflow. The JSON shape of consolidated findings, attribution fields, the optional self-signal, and the verify_output self-check protocol. Loaded into each judge subagent via --skill.
Output contract for stack-wide judge subagents in pr-workflow. The JSON shape with per-PR and cross-PR findings, attribution fields, optional self-signal, membership rules, and the verify_output self-check protocol. Loaded into each stack-judge subagent via --skill.
| name | github-pr-merge-convention |
| description | PR merge strategy, branch cleanup and post-merge hygiene for any pull request. Use when merging a PR, cleaning up after a merge or deciding how to land changes. See github-pr-stack-convention when PRs depend on other PRs. |
This skill covers how to merge pull requests and clean
up afterwards. It applies to every PR, whether standalone
or part of a stack. For stack-specific ordering and
safety rules, see github-pr-stack-convention.
Use a regular merge commit by default. This preserves the branch's commit history on the target branch, which matters: individual commits carry context (why a change was made, what test drove it, what refactor followed). Squashing throws that away.
gh pr merge NUMBER --merge
If a repository has its own merge strategy configured or documented, follow that instead. The repo's convention wins over this default.
Always delete the remote branch after merging to the default branch. There is no reason to keep merged branches around; they clutter the branch list and create ambiguity about what's still in flight.
For standalone PRs (no other open PR uses this branch as its base):
gh pr merge NUMBER --merge --delete-branch
The --delete-branch flag handles both the remote
branch and the local tracking branch in one step.
Do not use --delete-branch when the PR is part of
a stack. The CLI's --delete-branch deletes via a
separate API call, which auto-closes any PR that uses
the deleted branch as its base. Those PRs can't be
reopened. See github-pr-stack-convention for the
safe merge sequence.
After the merge, clean up the local checkout:
git switch main && git pull
git fetch --prune
git branch -d branch-name
If multiple branches were merged (after completing a stack, for example), batch the cleanup:
git switch main && git pull
git fetch --prune
git branch -d branch-1 branch-2 branch-3
--delete-branch when other open PRs depend
on the branch. It auto-closes dependents permanently.
See github-pr-stack-convention.