mcpField
P
pr-submit

pr-submit

github.com/pipecat-aiDevelopment16.9k41 installsUpdated today
Repository

About pr-submit

A skill that submits the current repository changes as a GitHub pull request. It guides branch and commit preparation, prose review, PR creation, and follow-up changelog and description updates.

Key features

  1. 01Checks repository status and recent commits
  2. 02Creates a branch and commits changes
  3. 03Runs prose review before pushing
  4. 04Creates a pull request with gh
  5. 05Updates changelog and PR description

Use cases

  1. 01Submitting local changes as a pull request
  2. 02Preparing commits and PR text for review

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/pipecat-ai/pipecat --skill pr-submit

After installing, type/pr-submitin Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported