# PR Submit

Create and submit a GitHub PR from the current branch

- Repository: https://github.com/pipecat-ai/pipecat (16982 stars)
- Category: Git and review
- License: BSD-2-Clause
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add pipecat-ai/pipecat --skill pr-submit -g -a claude-code -y`
Codex: `npx skills add pipecat-ai/pipecat --skill pr-submit -g -a codex -y`
Cursor: `npx skills add pipecat-ai/pipecat --skill pr-submit -g -a cursor -y`
Gemini CLI: `npx skills add pipecat-ai/pipecat --skill pr-submit -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add pipecat-ai/pipecat`

## Description

Create and submit a GitHub PR from the current branch

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

Submit the current changes as a GitHub pull request.

## Instructions

1. Check the current state of the repository:
   - Run `git status` to see staged, unstaged, and untracked changes
   - Run `git diff` to see current changes
   - Run `git log --oneline -10` to see recent commits

2. If there are uncommitted changes relevant to the PR:
   - Ask the user if they want a specific prefix for the branch name (e.g., `alice/`, `fix/`, `feat/`)
   - Create a new branch based on the current branch
   - Commit the changes using multiple commits if the changes are unrelated

3. Run `/prose-review branch` and fix anything it flags. Do this before pushing,
   while corrections are still cheap.

4. Push the branch and create the PR:
   - Push with `-u` flag to set upstream tracking
   - Create the PR using `gh pr create`

5. After the PR is created:
   - Run `/changelog <pr_number>` to generate changelog files, then commit and push them
   - Run `/pr-description <pr_number>` to update the PR description

   Both skills review their own prose, no separate pass is needed here.

6. Return the PR URL to the user.

Commit messages are prose too, `/prose-review` reads diffs and so won't see them.
Read the messages in `git log main..HEAD` against the same standard before pushing.