What problem does it solve?
When multiple agents or contributors produce many ready pull requests, merging them manually creates a stampede of stale branches, failed checks, and conflicting merges. This Skill serializes mainline landing so only one candidate is refreshed, verified, merged, and deployed at a time.
Core Features & Use Cases
- Queue-based landing: Scans
.planning/pr-readiness reports or accepts explicit PR URLs to build a durable landing queue in .planning/deploy-steward/queue.jsonl.
- Lease-protected serialization: Acquires a steward lease so no two runs merge into the same target simultaneously.
- Safe merge gating: Refreshes live PR state with the GitHub CLI, updates stale branches, waits for pending checks, and merges only when checks pass on the current head commit.
- Repair task generation: Opens intake repair tasks for failed checks, conflicts, or closed PRs instead of forcing merges.
- Use Case: A team running parallel coding agents ends the day with eight ready PRs; the steward rebases each against main, waits for CI, merges them one at a time, runs the deploy command after each merge, and files repair tasks for the two that fail.
Quick Start
Ask the agent to run the deploy steward in dry-run mode to scan ready PRs and show what it would merge before doing a live run.