Skip to content
Get packs

Guide · Agent skill

How to use the Open Pull Request agent skill (open-pr)

Updated · written with AI from the project's own documentation and checked against our catalogue data

The open-pr skill is a set of instructions that lets an AI agent open or update a pull request on the pascalorg/editor repository from the branch you are working on. This guide explains what the skill does, how to install it, how to trigger it with plain requests, and what it needs and how it behaves. By the end you will know how to get the agent to ship a small branch with a PR description that matches the actual commits and diff.

Open Pull Requestpascalorg/editor · MIT

Quick start

  1. 1Download the ZIP. Download the open-pr skill ZIP from this page.
  2. 2Unzip into a skills folder. Unzip it into ~/.claude/skills/ for personal use or a project's .claude/skills/ folder for one project.
  3. 3Or upload in the Claude apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the skill.
  4. 4Check git and gh. Make sure git is installed and the GitHub CLI (gh) is authenticated with an account that can push to and open PRs on pascalorg/editor.
  5. 5Commit your branch. Make sure you are on a branch other than main and that your work is committed.
  6. 6Ask for the PR. Tell the agent to open or update a pull request for the current branch in the editor repo.
  7. 7Review the report. Check the PR URL, title, the checks that were run, and any items left for the reviewer.

What does the open-pr skill make the agent do?

The skill is written for the pascalorg/editor repository. When you ask the agent to open or update a pull request, it first inspects the current branch: it checks the branch name, confirms there is nothing uncommitted that you did not ask it to commit, and reads the commits and diff against origin/main.

It then fills in the repository's .github/pull_request_template.md, writes a title, and pushes the branch. It creates the pull request or edits an existing one using the GitHub CLI (gh). It finishes with a short report giving the PR URL, the title, which checks it ran, and anything left unchecked for the reviewer.

  • Describes only the commits and diff on the branch, not work that arrived by merging main, reverted commits, or patch-equivalent cherry-picks.
  • Stops and asks you if a changed file has no commit on the branch explaining it.
  • Never claims a check it did not run.
  • Keeps the media section and the reviewer's checklist ticks when updating an existing PR.

Install the open-pr skill

Download the ZIP of the skill from this page. Unzip it into one of these locations, depending on how you want it available:

Use ~/.claude/skills/ in your home directory to make the skill available across your projects. Use a project's .claude/skills/ folder to make it available only in that project.

If you use the Claude apps instead, upload the skill under Settings → Capabilities → Skills.

  • Personal install: unzip into ~/.claude/skills/ so the open-pr folder containing SKILL.md sits there.
  • Project install: unzip into the project's .claude/skills/ folder.
  • Claude apps: upload the skill under Settings → Capabilities → Skills.

Check the requirements before you start

The skill needs git and the GitHub CLI (gh). The gh account must be authenticated and able to push to and open pull requests on pascalorg/editor. The repository must contain .github/pull_request_template.md, because the skill fills that template in.

The skill runs scripts and uses the network, since it pushes branches and calls GitHub.

  • git installed and the repository cloned
  • GitHub CLI (gh) installed and authenticated with an account that can push to pascalorg/editor
  • Read access to .github/pull_request_template.md in the repo

Trigger the skill with a natural request

You do not need a special command. The skill is meant to be triggered when you ask the agent to open or create a PR, push and open a PR, or ship a branch in the editor repo. Be clear about the branch you are on, and make sure your work is committed first.

Examples of requests that match the skill's description:

  • Open a PR for this branch.
  • Push this branch and open a pull request.
  • Create a PR for my changes in the editor repo.
  • Update the open PR for this branch with the latest commits.
  • Ship this branch to pascalorg/editor.

Review the result and tips for good results

The agent's report lists the PR URL, the title and which checks it ran. Read the description before a reviewer does, especially the How to test section, because it should reflect the real steps taken. Checks the agent did not run are listed as unchecked for you or the reviewer.

Keep branches small and committed with clear messages, since the description is built from those commits. If the agent stops and asks about a file, answer by explaining the change or committing it on its own.

  • Commit your work before asking, so the branch is clean.
  • Use one focused change per branch so the description stays accurate.
  • Expect a title under about 70 characters with a scope prefix such as core:, viewer:, editor:, nodes:, or mcp: when one package owns the change.
  • Only tick checklist items you have verified yourself.

What people use it for

  • Opening a PR for a small bug fix on a feature branch, with the description limited to the actual commits.
  • Pushing new commits to an existing PR and having the agent refresh the What and How to test sections.
  • Filling in the repo's PR template consistently across several contributors' branches.
  • Shipping a branch in one step: push, create the PR, and get a report of what was checked.

Frequently asked questions

Is the open-pr skill free and what is its licence?

The skill is listed under the MIT licence. The source text does not mention pricing, so check the page for any other terms before relying on it.

What do I need to install the open-pr skill?

You need the ZIP from this page, a place to unzip it (~/.claude/skills/ or a project's .claude/skills/), or the Claude apps to upload it under Settings → Capabilities → Skills. To run it, you also need git and an authenticated GitHub CLI (gh) account that can open PRs on pascalorg/editor.

Can I use the open-pr skill on other repositories?

No. The skill is written for pascalorg/editor. Its paths, title scopes and template assumptions are specific to that repository, so it is not meant for other repos.

Why did the agent stop and ask me questions?

The skill stops when the branch has uncommitted changes you did not ask it to commit, or when a changed file has no commit on the branch explaining it. This prevents publishing work that the PR description cannot honestly describe. Commit or explain the change and ask again.

Does the skill run commands on my machine and access the network?

Yes. The skill runs scripts and uses the network, because it runs git and gh commands, pushes the branch and creates or edits the pull request on GitHub. Only install it if you are comfortable with those actions on your repository.

What should I use instead of open-pr?

If you work on a repository other than pascalorg/editor, or prefer to write PR descriptions yourself, use the GitHub CLI or web interface directly. The source does not name other specific alternatives.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use open-pr if you contribute to pascalorg/editor and want the agent to push branches and write accurate, template-based PR descriptions from the real commits and diff. Pick something else if you work in other repositories, or if you want full manual control over each PR description and check run.

Download the skill