with one click
open-pr
// Publish the current branch and open a pull request to the upstream Mudlet repository. Generates a concise, non-technical PR title and description following the project template.
// Publish the current branch and open a pull request to the upstream Mudlet repository. Generates a concise, non-technical PR title and description following the project template.
| name | open-pr |
| description | Publish the current branch and open a pull request to the upstream Mudlet repository. Generates a concise, non-technical PR title and description following the project template. |
| argument-hint | Optional hint about what this PR does (e.g. "adds shimmer blink effect") |
| user-invocable | true |
| disable-model-invocation | true |
Use this skill when the user asks to open a pull request, create a PR, or push their changes upstream. The skill publishes the current branch if needed and opens a PR against the upstream development branch.
Gather context: Run git diff upstream/development...HEAD to understand what changed. Also run git log upstream/development..HEAD --oneline for commit messages and git branch --show-current for the branch name.
Determine the PR title prefix based on the nature of the changes:
Fix: โ for bug fixesImprove: โ for enhancements to existing functionalityAdd: โ for new features or capabilitiesInfrastructure: โ for build system, CI, tooling, or project configuration changesGenerate the PR title: After the prefix, write a short, non-technical summary that anyone can understand. This title appears in PTB changelogs.
Generate the PR body using this exact template format:
#### Brief overview of PR changes/additions
<1-3 sentences summarizing what changed, written for a non-technical audience>
#### Motivation for adding to Mudlet
<1-2 sentences explaining why this change is valuable>
#### Other info (issues closed, discussion etc)
<Any related issues, discussions, or notes โ or "None" if not applicable>
Show the draft title and body to the user and ask for confirmation before proceeding.
Publish the branch if it has not been pushed to the user's fork yet:
git push -u origin <branch-name> to push and set the upstream tracking branch.Open the pull request using the mcp_github_create_pull_request tool:
owner: Mudletrepo: Mudletbase: developmenthead: <fork-owner>:<branch-name> (e.g. mpconley:feature/my-branch)title: The generated PR titlebody: The generated PR bodyTo determine <fork-owner>, parse it from the origin remote URL.
Report the result: Show the user the PR URL on success, or the error details on failure.