A well-made pull request saves time for reviewers and helps your code get merged faster. This guide covers the steps to create a pull request in the warp repository. You will learn to merge the latest master, run presubmit checks, and link your changes to a Linear task.
Before you open a pull request, make sure to merge master into your branch. Run the presubmit script to check formatting, linting, and tests. Review your changes carefully. Include tests when needed for bug fixes or new features.
When you are ready, use the GitHub CLI to create your pull request. Use the PR template and add a clear title with the Linear issue ID. This makes it easy for your team to review and approve your work.
Global
mkdir -p ~/.claude/skills/create-prProject
mkdir -p .claude/skills/create-prSource Repository
Caveman Commitjuliusbrussee/caveman
Generate ultra-compressed commit messages with Conventional Commits format
Verification Before Completionobra/superpowers
Always run fresh verification before claiming work is complete or passing
Git Guardrails Claude Codemattpocock/skills
Stop dangerous git commands from running automatically with safety hooks
Setup Pre Commitmattpocock/skills
Automate code formatting type checking and tests before every commit
Using Git Worktreesobra/superpowers
Isolate your feature work with git worktrees and keep your main branch safe
Finishing A Development Branchobra/superpowers
Finish your development branch with merge, pull request, or cleanup options
Resolving Merge Conflictsmattpocock/skills
Resolve Git merge conflicts step by step preserving both intents
Git Commitgithub/awesome-copilot
Automatically write standardized git commits by analyzing your code changes