create-pr · ulpi-io — Claude Code skill: what it does, how to install
create-pr opens a GitHub pull request from the real branch diff: commits pending work first, runs the narrowest checks, pushes, then creates and verifies the PR with gh.
no license 156 installs ★ 5 updated 2026-08-31
npx skills add ulpi-io/skills --skill create-pr -a claude-codeWhat create-pr does
The skill builds a pull request from the full diff against the true base branch. Branch names and commit messages only hint at what happened. It looks at the current branch, its tracking state, uncommitted files and how far ahead of base you are. A dirty tree is not ignored: the commit skill runs first, then the workflow picks up again.
Readiness comes next. A branch sitting on main, master or develop, an empty branch, or conflict markers in changed files stop everything. Classification — type, scope, breaking changes — is read off the code, with references/pr-conventions.md loaded for the heuristics. Then the narrowest checks that fit the touched files run: typecheck, lint, a scan for conflict markers. Lint and type failures are warnings; conflict markers always block, and test status never gets invented in the body.
The branch is pushed before gh pr create runs, and afterwards the skill checks the number, URL, state, draft flag and base. No gh on the machine means no PR: you get a prepared title, body and compare URL to open it by hand. It stays user-only, so nothing fires until you ask for a PR, and it asks back when the base or reviewers are unclear.
What it helps with
- open a PR that matches the diff rather than the branch name
- commit leftover changes before the PR is drafted
- catch conflict markers in changed files before pushing
- spell out breaking changes in the PR body
- confirm the new PR's number, URL and state right after creation
Example prompts for the agent
- Open a draft PR against
mainand add the backend team as reviewers. - Push this branch and create a pull request describing what actually changed.
- Make a PR for the current branch with a Conventional Commit title.
How to install create-pr
1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill create-pr -a claude-code2Manually: put the files in place
~/.claude/skills/create-pr/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/create-pr/
1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill create-pr -a codex2Manually: put the files in place
.agents/skills/create-pr/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill create-pr -a cursor2Manually: put the files in place
.cursor/skills/create-pr/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ulpi-io/skills create-pr2Manually: put the files in place
.github/skills/create-pr/SKILL.md1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill create-pr -a gemini-cli2Platform CLI
gemini skills install https://github.com/ulpi-io/skills --path create-prManually: put the files in place
.devin/skills/create-pr/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill create-pr -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about create-pr
How do I install create-pr in Claude Code?
Run npx skills add ulpi-io/skills --skill create-pr -a claude-code. The skill lands at ~/.claude/skills/create-pr/SKILL.md.
What does create-pr do?
It reads the branch diff against the real base, checks that the branch is ready, classifies the change, pushes the branch and opens a pull request with gh, then verifies its number, URL and state.
What happens if gh is not installed?
No pull request is created. The skill stops and hands you the prepared title, body and compare URL so you can open it yourself.
Similar skills
All skills for Git and GitHub →create-pr by other authors comes first.