CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-submit

Create and submit a GitHub PR from the current branch

63

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/pr-submit/SKILL.md
SKILL.md
Quality
Evals
Security

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.

Repository
pipecat-ai/pipecat
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.