Put the requested PRs into a single stack in optimal merge order. Resolve merge conflicts.
Use the supplied PR list, or discover all open PRs in the current repository when the user asks for all current PRs.
- Inspect the PRs and Git history to understand their dependencies.
- Choose an order that respects dependencies and minimizes expected conflict-resolution work.
- Update the branches and PR bases to form that stack, resolving conflicts while preserving the intended changes.
- Verify the resulting chain and report the order, conflicts resolved, and anything that remains blocked or incomplete.
Rely on CI for validation. Do not run, wait for, or fix local tests, lint, builds, CI, or review checks, even after resolving conflicts. Preserve unrelated work and respect repository protections. Before each publication write, verify auto-merge is disabled for every selected PR; stop and report a blocker if enabled or unverifiable. Do not disable auto-merge yourself. Do not merge the PRs into the root branch or close them. Honor preview-only requests without publishing changes. Stop rather than guess when a conflict requires an unclear product decision.