What problem does it solve? Opening a pull request involves repetitive manual steps: gathering branch context, pushing commits, linking issues, filling the PR template, and verifying acceptance. For cross-layer features, a single PR cannot merge safely because clients call server contracts that do not exist on the trunk yet, requiring a careful split into ordered stacked PRs. ## Core Features & Use Cases - Automated PR Creation: Gathers git context in parallel, pushes the branch, searches related GitHub and Linear issues, fills the PR template, and opens the PR against canary via gh pr create. - Acceptance Gate Enforcement: Requires a published acceptance round link in the PR body before opening, or an explicit skip reason for changes with no user-visible outcome. - Stacked PR Splitting: Splits one cross-layer branch (database, shared package, server TRPC, desktop/CLI/UI) into ordered PRs where the server contract merges before its callers, using backup branches, reset --hard, and --force-with-lease. - Use Case: A feature branch adds a new TRPC procedure plus desktop and CLI callers. The skill rewrites the branch into a server-only PR targeting canary and a client PR stacked on top, so each layer merges safely in order. ## Quick Start Ask the assistant to create a PR for the current branch, or to split this branch into stacked PRs so the backend merges first.