gh-batch-runnerlisted

# GitHub Batch Runner ## Overview Implement several Issues as one release: one integration branch, one verification of the whole, one Pull Request. Per-Issue implementation follows the `gh-issue-resolver` contract unchanged — this skill owns only what is batch-level: membership, ordering, whole-branch verification, and the single PR. Use this skill only when the answer to **"do these ship together?"** is yes. Independent Issues use `gh-issue-resolver` once per Issue; a dependency chain that ships separately uses the stacked flow (also `gh-issue-resolver`, with the dependency's branch as base). ## Prerequisites - **Every member Issue has an agreed plan comment** (`<!-- gh-issue-planner:agreed-plan -->`) posted by `gh-issue-planner`. If any Issue lacks one, stop and run the planner for that Issue first — planning several Issues in one pass is supported there. - The repository's **integration branch** is known (CLAUDE.md `## Flow`; falls back to the default branch). ## Workflow ### Step 1: Collect the batch under an Epic Issue The batch's membership is an Epic Issue holding the members as sub-issues — not a branch name, not a comment convention. Create the Epic if the user did not name one: ```bash gh issue create --title "Epic: <what ships together>" --label epic --body "$(cat <<'EOF' ## まとめて対応する Issue <one line per member Issue> ## 統合先 <integration branch> --- <!-- gh-batch-runner:batch-plan --> *Generated by `gh-batch-runner`. Membership is the sub-issue li