
Create Pull Request
This handles the full PR creation workflow, from checking if gh CLI is installed to analyzing your commits and generating a meaningful PR title. The smart part is how it looks at your commit history and branch name to avoid generic titles like "initial commit" or "fix." It checks for existing PRs first, validates prerequisites, and will even invoke related skills like ci-fix or code review before letting you submit. The conventional commits detection is nice if your project uses that format. One thing to know is it's opinionated about git hygiene and will suggest rebasing or squashing messy commits, which some teams might not want.
- skills.sh installs
- 177
- GitHub stars
- 824
- last updated
- Aug 21, 2026
Install
$ npx -y skills add warpdotdev/oz-skills --skill create-pull-request --agent claude-codeInstalls into .claude/skills of the current project.
Files
Create Pull Request
This skill guides you through creating a well-structured GitHub pull request that follows project conventions and best practices.
Prerequisites Check
Before proceeding, verify the following:
1. Check if gh CLI is installed
gh --version
If not installed, inform the user:
The GitHub CLI (
gh) is required but not installed. Please install it:
- macOS:
brew install gh- Other: https://cli.github.com/
2. Check if authenticated with GitHub
gh auth status
If not authenticated, guide the user to run gh auth login.
3. Check for related skills
Before creating a PR, check if any skills are available that relate to code review, CI, or testing. These should be invoked first as prerequisites.
Look for skills with descriptions containing:
- "review" (e.g., code review, PR review, web-design-guidelines)
- "CI" or "ci-fix" (e.g., fixing CI failures)
- "testing" or "test" (e.g., running tests, webapp-testing)
Sponsors
Details
- Repository
- github.com/warpdotdev/oz-skills
- Categories
- Git & Pull Requests, Code Review & Quality, CLI & Terminal
- First seen
- Jun 3, 2026