How do I install the Create Pr skill?

Run npx skillmds@latest add uniswap/create-pr in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Create Pr safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Create Pr?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Create Pr free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Create Pr?

uniswap (@uniswap) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Create Pr by uniswap — Agent Skill

Name: Create Pr
Author: uniswap

Create Pr

Create or update pull requests with conventional commits. Use when user says "create a PR for these changes", "submit this for review", "open a pull request", "push these changes and create a PR", "I'm ready to submit this work", or "create PR and link to issue

uniswap 4923d74 3.0 KB Updated Sep 17, 2026

File contents

PR Creator

Create or update pull requests with auto-generated conventional commits and descriptions. Supports both standard Git + GitHub CLI (default) and Graphite workflows.

What It Does

Analyze Diff: Run git diff origin/<target>...HEAD to inspect all changed files
Detect Change Type: Classify as feat, fix, refactor, etc. based on the diff
Generate Commit: Use commit-message-generator-agent to draft a conventional commit message, then ask user to confirm before staging/committing
Create PR Title: <type>(<scope>): <description>
Write Description: Comprehensive PR body (summary, modified files, testing notes, linked issues)
Submit: Use gt submit (Graphite) or gh pr create (default)

Error Handling

No changes / no commits ahead of target: Stop and inform the user — there is nothing to submit
PR already exists for this branch: Switch to update mode; run git push to publish the latest commits (use gt submit for Graphite). If the PR title or body also need updating, read the live body first (gh pr view <n> --json body -q .body) and edit from it — never regenerate the body from scratch. The author may have hand-edited the description or pasted images/screenshots (![](https://github.com/user-attachments/...)) that exist only in the live body, not in any file; overwriting silently destroys them. Splice your change into the current body and apply with gh pr edit <n> --body-file <tmp>.
User rejects commit message: Re-generate with user-provided guidance, then confirm again before proceeding

Conventional Commit Types

Type	Use
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation
`style`	Formatting
`refactor`	Code restructure
`perf`	Performance
`test`	Tests
`build`	Build system
`ci`	CI config
`chore`	Maintenance

PR Description Includes

Summary of changes
List of modified files with rationale
Testing information
Related issues

Commit Policy

Always asks user before committing. Never auto-commits.

Options

Custom target branch (default: main)
Breaking change detection
Issue linking
PR creation method: standard git + GitHub CLI (default) or Graphite (--use-graphite)
Stack-aware creation (only with Graphite)
Update existing vs create new

Examples

"Create a PR for these changes"
"Submit this for review"
"Create PR and link to issue #123"
"Mark as breaking change due to API updates"

Output

Provides PR URL after creation for review.

---name: create-prdescription: Create or update pull requests with conventional commits. Use when user says "create a PR for these changes", "submit this for review", "open a pull request", "push these changes and create a PR", "I'm ready to submit this work", or "create PR and link to issue---# PR CreatorCreate or update pull requests with auto-generated conventional commits and descriptions. Supports both standard Git + GitHub CLI (default) and Graphite workflows.## What It Does1. **Analyze Diff**: Run `git diff origin/<target>...HEAD` to inspect all changed files2. **Detect Change Type**: Classify as feat, fix, refactor, etc. based on the diff3. **Generate Commit**: Use `commit-message-generator-agent` to draft a conventional commit message, then ask user to confirm before staging/committing4. **Create PR Title**: `<type>(<scope>): <description>`5. **Write Description**: Comprehensive PR body (summary, modified files, testing notes, linked issues)6. **Submit**: Use `gt submit` (Graphite) or `gh pr create` (default)## Error Handling- **No changes / no commits ahead of target**: Stop and inform the user — there is nothing to submit- **PR already exists for this branch**: Switch to update mode; run `git push` to publish the latest commits (use `gt submit` for Graphite). If the PR title or body also need updating, **read the live body first** (`gh pr view <n> --json body -q .body`) and edit *from* it — never regenerate the body from scratch. The author may have hand-edited the description or pasted images/screenshots (`![](https://github.com/user-attachments/...)`) that exist only in the live body, not in any file; overwriting silently destroys them. Splice your change into the current body and apply with `gh pr edit <n> --body-file <tmp>`.- **User rejects commit message**: Re-generate with user-provided guidance, then confirm again before proceeding## Conventional Commit Types| Type | Use || ---------- | ---------------- || `feat` | New feature || `fix` | Bug fix || `docs` | Documentation || `style` | Formatting || `refactor` | Code restructure || `perf` | Performance || `test` | Tests || `build` | Build system || `ci` | CI config || `chore` | Maintenance |## PR Description Includes- Summary of changes- List of modified files with rationale- Testing information- Related issues## Commit Policy**Always asks user before committing.** Never auto-commits.## Options- Custom target branch (default: main)- Breaking change detection- Issue linking- PR creation method: standard git + GitHub CLI (default) or Graphite (`--use-graphite`)- Stack-aware creation (only with Graphite)- Update existing vs create new## Examples```"Create a PR for these changes""Submit this for review""Create PR and link to issue #123""Mark as breaking change due to API updates"```## OutputProvides PR URL after creation for review.

Frequently asked questions