relay-mergelisted

## Inputs - Env: optional `RELAY_SKILL_ROOT` defaults to `skills`. - Files: reviewed PR, retained run manifest/worktree, optional sprint file, and follow-up issue text. - Sibling scripts: `${RELAY_SKILL_ROOT:-skills}/relay-merge/scripts/gate-check.js`, `${RELAY_SKILL_ROOT:-skills}/relay-merge/scripts/finalize-run.js`, `${RELAY_SKILL_ROOT:-skills}/relay-merge/scripts/append-learnings.js`. # Relay Merge ## Use when - Merging a PR after `relay-review` returns LGTM/pass - Finalizing the retained run manifest, worktree, and branch cleanup - Recording sprint-file and follow-up issue updates after merge ## Do not use when - Reviewing executor output — use `relay-review` - Delegating implementation or review fixes — use `relay-dispatch` - Authoring rubrics or dispatch prompts — use `relay-plan` - Shaping an ambiguous task before planning — use `relay-ready` Explicitly merge a ready-to-merge PR and close the loop. **Requires relay-review PR comment.** ## Process ### 0. Gate check — verify relay-review completed ```bash node "${RELAY_SKILL_ROOT:-skills}/relay-merge/scripts/gate-check.js" $PR_NUM ``` - Exit 0 (LGTM) → PR is ready to merge; proceed only if the user wants to land it now - Exit 1 (no comment) → **STOP.** Run relay-review first - Exit 1 (stale LGTM) → **STOP.** Run relay-review again for the latest commit - Exit 1 (CHANGES_REQUESTED) → **STOP.** Re-dispatch or fix the branch first - Exit 1 (ESCALATED) → **STOP.** Show unresolved issues to user **Intentional skip*