
Create Pr
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.
- skills.sh installs
- 28.7K
- GitHub stars
- 684
- last updated
- Aug 21, 2026
Install
$ npx -y skills add warpdotdev/common-skills --skill create-pr --agent claude-codeInstalls into .claude/skills of the current project.
Files
create-pr
Overview
This guide covers best practices for creating pull requests in the warp repository, including merging master, validating changes efficiently, linking Linear tasks, ensuring appropriate test coverage, and structuring your PR for effective review.
Related Skills
write-pr-description- Write the PR body itself: template sections, prose, and reviewer guidancefix-errors- Fix targeted compilation, test, lint, or formatting failures before opening a PRwarp-integration-test- Add or update integration coverage for user-visible flows, regressions, and P0 use casesadd-feature-flag- Gate changes behind feature flags
Pre-PR Checklist
1. Merge master into your feature branch
Always merge master into your feature branch before starting the review process.
git fetch origin
git merge origin/master
Resolve any merge conflicts locally before opening the PR.
2. Review your changes
Before creating a PR, review what changes you're about to submit:
# View commits in your branch (comparing against base branch)
git --no-pager log <base-branch>..HEAD --oneline
Sponsors
Details
- Repository
- github.com/warpdotdev/common-skills
- Categories
- Git & Pull Requests, Code Review & Quality
- First seen
- May 16, 2026
More from warpdotdev/common-skills
All 23- Update Skill28.6K
- Diagnose Ci Failures28.6K
- Pr Walkthrough28.3K
- Brandalf28.3K
- Council28.1K
- Check Impl Against Spec27.1K
- Reproduce Bug Report27K
- Respond To Pr Comments In Blocklist25.3K
- Validate Changes Match Specs25.3K
- Cross Critique22.1K
- Research22K
- Saga20.8K
- Write Feature Docs19.3K
- Scan New Specs19.3K
- Readout17.7K
- Review Pr29.1K
- Spec Driven Implementation28.9K
- Write Product Spec28.9K
- Write Tech Spec28.8K
- Resolve Merge Conflicts28.8K
- Fix Errors28.7K
- Implement Specs28.7K