This handles the full workflow for opening a pull request in the Warp repository, from merging master and running presubmit checks to linking Linear tasks and structuring your PR description. It's opinionated about testing requirements: bug fixes need regression tests, algorithmic code needs unit tests, UI components need layout validation, and P0 use cases need integration coverage. The guide will actually ask you before skipping integration tests if your changes look like they need them. It covers the gh CLI commands for creating and updating PRs, includes co-author attribution for agent contributions, and enforces running cargo fmt and clippy before any code-changing commit. Basically a checklist that knows the Warp team's standards.
npx skills add https://github.com/warpdotdev/common-skills --skill create-pr