pipecat-ai/pipecat

pr-submit

Create and submit a GitHub PR from the current branch

First seen Feb 28, 2026

Installation

$ npx skills add pipecat-ai/pipecat --skill pr-submit

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from pipecat-ai/pipecat.

npx skills add pipecat-ai/pipecat

Browse all from pipecat-ai/pipecat

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 15.3K
License LICENSE
Default branch main
Open issues 107
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,381 B
  • docs SUMMARY.md 70 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 35 installs

SKILL.md

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

  1. 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

  1. Run /prose-review branch and fix anything it flags. Do this before pushing,

while corrections are still cheap.

  1. Push the branch and create the PR:

- Push with -u flag to set upstream tracking - Create the PR using gh pr create

  1. After the PR is created:

- Run /changelog <prnumber> to generate changelog files, then commit and push them - Run /pr-description <prnumber> to update the PR description

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

  1. 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.