Open or update pull requests for the pascalorg/editor repository using git and GitHub CLI.
- GitHub stars
- 25,443
- Files
- 1
- Last commit
- Nov 11, 2026
- License
- MIT
- Allowed tools
- 6
What does the open-pr skill do?
open-pr is an agent skill. Open or update pull requests for the pascalorg/editor repository using git and GitHub CLI.
Summary generated from the skill's SKILL.md.
About the open-pr skill
Managing pull requests for the pascalorg/editor repository becomes automated when an agent uses this skill to handle branch shipping. It works by analyzing the current git branch to identify exactly which commits and file changes are present compared to the main branch. This ensures the resulting pull request description only includes relevant work and avoids including merged changes or cherry-picks.
An agent should load this tool when a user wants to push a branch, create a new pull request, or update an existing one. The process relies on git for branch analysis and the GitHub CLI for interacting with the repository. It follows the specific pull request template found in the repository to populate headings, testing instructions, and checklists. The skill produces a formatted pull request with a scoped title and a detailed body that includes specific verification steps and local check results.
What an agent can do with it
- 1Create a new pull requestAsk the agent to open a pull request for the current branch in the editor repository.
- 2Update an existing pull requestRequest that the agent refreshes a pull request with new changes from the current branch.
- 3Generate accurate PR descriptionsHave the agent write a description based strictly on the actual git diff and commit history.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the open-pr skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the open-pr skill in Claude Code
~/.claude/skills/open-pr/SKILL.md
$ npx degit pascalorg/editor/.agents/skills/open-pr ~/.claude/skills/open-prInstall the open-pr skill in Claude Code (project)
.claude/skills/open-pr/SKILL.md
$ npx degit pascalorg/editor/.agents/skills/open-pr .claude/skills/open-prInstall the open-pr skill in Codex
~/.agents/skills/open-pr/SKILL.md
$ npx degit pascalorg/editor/.agents/skills/open-pr ~/.agents/skills/open-prInstall the open-pr skill in Gemini CLI
~/.gemini/skills/open-pr/SKILL.md
$ npx degit pascalorg/editor/.agents/skills/open-pr ~/.gemini/skills/open-prInstall the open-pr skill in Claude.ai
npx degit pascalorg/editor/.agents/skills/open-pr open-pr && zip -r open-pr.zip open-pr # claude.ai → Customize → Skills → + → Create skill → Upload a skill → open-pr.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablepascalorg/editor/.agents/skills/open-pr is public and reachablegithub.com/pascalorg/editor/tree/HEAD/.agents/skills/open-pr ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-11github.com/pascalorg/editor/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/pascalorg/editor/blob/HEAD/.agents/skills/open-pr ↗Pass
- Pre-approved tools are scopedPre-approved: Bash(git, *), Bash(gh, *), Read, Writegithub.com/pascalorg/editor/blob/HEAD/.agents/skills/open-pr ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 51 linesgithub.com/pascalorg/editor/blob/HEAD/.agents/skills/open-pr ↗Pass
SKILL.md
View on GitHubOpen (or refresh) a pull request against pascalorg/editor from the current branch.
1. What is actually on the branch
git branch --show-current # not main
git status --short # nothing uncommitted you weren't asked to commit
base=$(git merge-base HEAD origin/main)
git log --oneline --first-parent --no-merges "$base"..HEAD
git diff --stat "$base"..HEAD
The PR describes only these commits and this diff. Work that arrived by merging main, reverted commits, and patch-equivalent cherry-picks are not this PR's claims. If a file in the diff has no commit on the branch explaining it, stop and ask.
Run relevant local checks; reuse checks that already cover the change. CI runs the required suite. Never claim a check you did not run.
2. Body = the repo template
.github/pull_request_template.md is the source of truth for headings and checklist. Fill it from §1, not from memory:
- What does this PR do? — the result, one paragraph or a short list;
Fixes #123when applicable. - How to test — numbered, concrete reviewer steps with the expected outcome. Automated commands only if you ran them.
- Screenshots / screen recording — link,
Not added yet.for a visual change without media, orN/A — non-visual change. - Checklist — copy verbatim; tick only what was verified (
bun devonly after a real local run).
Title: under ~70 characters, a concrete result (not "update"/"improve"), scope-prefixed when one package owns it (core:, viewer:, editor:, nodes:, mcp:).
3. Push and open, or update
git push -u origin HEAD
gh pr view --json number,url,body 2>/dev/null # existing PR?
- None → write the description to a file, then
gh pr create --title … --body-file <file>. - Exists →
gh pr edit <n> --body …: rebuild "What" and "How to test" from the current branch, keep the media section and the reviewer's checklist ticks verbatim, keep any extra sections at the end. Change the title only if the scope changed.
End the body with the attribution lines the session asks for, if any.
4. Report
PR URL, title, which checks you ran, and anything left unchecked for the reviewer.
Files in this skill
1open-pr skill questions
How do I install the open-pr skill in Claude Code?
Run npx degit pascalorg/editor/.agents/skills/open-pr ~/.claude/skills/open-pr. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the open-pr skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How should the pull request description be formatted?
The description must follow the repository's template located at .github/pull_request_template.md, including sections for what the PR does, how to test, and a checklist.
What should I do if a file in the diff has no corresponding commit on the branch?
If a file in the diff lacks a commit on the branch explaining the change, you must stop and ask for clarification.
How does the tool handle existing pull requests?
If a pull request already exists, the tool updates it by rebuilding the 'What' and 'How to test' sections from the current branch while preserving media and checklist ticks.