- name
Open or update a pull request on pascalorg/editor from the current branch, describing only what the branch actually did. Use when the user asks to open/create a PR, push and PR, or ship a branch in th
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add pascalorg/editor --skill open-pr -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add pascalorg/editor --skill open-pr -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add pascalorg/editor --skill open-pr -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add pascalorg/editor --skill open-pr -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/pascalorg/editor/tree/HEAD/.agents/skills/open-prFrom the publisher
Open (or refresh) a pull request against pascalorg/editor from the current 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.
.github/pull_request_template.md is the source of truth for headings and checklist. Fill it from §1, not from memory:
Fixes #123 when applicable.Not added yet. for a visual change without media, or N/A — non-visual change.bun dev only 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:).
git push -u origin HEAD
gh pr view --json number,url,body 2>/dev/null # existing PR?
gh pr create --title … --body-file <file>.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.
PR URL, title, which checks you ran, and anything left unchecked for the reviewer.
© 2026 Skills Rack.
---name: open-prdescription: Open or update a pull request on pascalorg/editor from the current branch, describing only what the branch…---# .agents/skills/open-pr/SKILL.mdOverview
Open or update a pull request on pascalorg/editor from the current branch, describing only what the branch actually did. Use when the user asks to open/create a PR, push and PR, or ship a branch in the editor repo.
FAQ
Download .agents/skills/open-pr/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/pascalorg/editor.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.