What problem does it solve? Creating pull requests manually involves repetitive git and GitHub CLI steps, and cross-layer feature branches (database, server, clients) cannot merge safely as a single PR because callers depend on contracts that don't exist on the trunk yet. ## Core Features & Use Cases - Automated PR Creation: Gathers branch context, pushes changes, links related GitHub and Linear issues, and opens a PR against canary using the repository's PR template. - Stacked PR Splitting: Splits one cross-layer branch into ordered PRs so the server contract (TRPC, database schema) merges before its desktop, CLI, and UI callers. - Safety Guardrails: Uses backup branches, --force-with-lease, and explicit push targets to prevent accidental pushes to canary or lost commits. - Use Case: You finished a feature spanning packages/database, src/server, and apps/cli on one branch. Invoke this Skill to split it into a server PR and a stacked client PR, each closing only its own Linear issues. ## 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.