New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Pascal Editor PR Opener

by pascalorg in pascalorg/editor

Opens or refreshes a pull request on pascalorg/editor from the current branch, describing only what the branch's commits and diff actually contain.

MITAuto-check passedDevelopment

Install Pascal Editor PR Opener

skills CLI
$ npx skills add pascalorg/editor --skill open-pr -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install pascalorg/editor open-pr --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/pascalorg/editor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/open-pr .claude/skills/open-pr && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
open-pr
GitHub stars
25k
Token cost
~619 tokens
SKILL.md length
273 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Opens or refreshes a pull request on pascalorg/editor from the current branch, describing only what the branch's commits and diff actually contain.

  • Works in 4 steps: What is actually on the branch → Body = the repo template → Push and open, or update → …
  • Opening a pull request from a finished branch in the editor repo
  • SKILL.md covers 1. What is actually on the…, 2. Body = the repo template, 3. Push and open, or update and 4. Report
  • Calls git, gh and bun

What it does

The agent first establishes what is really on the branch: it is not main, nothing uncommitted is left unexplained, and the PR covers only the branch's own commits and diff, not work that arrived by merging main, reverted commits or cherry-picks. If a file in the diff has no commit explaining it, the agent stops and asks. For non-trivial changes it runs bun run check-types, and it never claims a check it did not run.

The PR body follows the repository template in .github/pull_request_template.md: what the PR does, with Fixes links where they apply, numbered how-to-test steps with expected outcomes, screenshots or a note that none were added, and the checklist copied as written with only verified items ticked. Titles stay under about 70 characters, state a concrete result and carry a scope prefix such as core, viewer, editor, nodes or mcp.

The agent pushes with git, checks with gh whether a PR already exists, and then either creates it or rebuilds the body of the existing one, keeping the media section and the reviewer's checklist ticks. It ends with a report of the PR URL, title, checks run and anything left unchecked for the reviewer. The skill is limited to git and gh commands and file reading.

When your agent uses it

  • Opening a pull request from a finished branch in the editor repo
  • Refreshing an existing PR's description after more commits
  • Writing a how-to-test section that reviewers can follow

Example prompts

  • “Push this branch and open a PR.”
  • “Update the PR description, since I added two more commits.”
  • “Ship this branch to pascalorg/editor with the template filled in and the type check run.”

Requirements

  • Git and the GitHub CLI (gh)
  • Bun, for the bun run check-types check
  • Pre-approved tools (allowed-tools): Bash(git *), Bash(gh *), Read

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. What is actually on the branch
  2. Body = the repo template
  3. Push and open, or update
  4. Report

What it can do on your machine

Read from SKILL.md and the folder at commit a860e19. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(git *)
    • Bash(gh *)
    • Read

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh
    • bun

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pascal Editor PR Opener loads about 619 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 273 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~56
When it runs · the whole SKILL.md, loaded when a task matches
~619

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from pascalorg/editor at commit a860e19, republished under its MIT licence (© pascalorg). 273 words, ~619 tokens.

Download SKILL.mdSave it as .claude/skills/open-pr/SKILL.md (or your agent's skills folder).
name
open-pr
description
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.
allowed-tools
Bash(git *), Bash(gh *), Read
metadata.internal
true

Open (or refresh) a pull request against pascalorg/editor from the current branch.

1. What is actually on the branch

bash
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 bun run check-types when the change is non-trivial; 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 #123 when 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, or N/A — non-visual change.
  • Checklist — copy verbatim; tick only what was verified (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:).

3. Push and open, or update

bash
git push -u origin HEAD
gh pr view --json number,url,body 2>/dev/null     # existing PR?
  • None → gh pr create --title … --body "$(cat <<'EOF' … EOF)".
  • 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.

© pascalorg, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/open-pr of pascalorg/editor.

Open the folder on GitHubat commit a860e19

Compare with similar skills

Pascal Editor PR Opener next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Pascal Editor PR Opener compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pascal Editor PR Opener this skillpascalorg/editor25k—~619Automated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Creating Description For Gh PRredis/jedis12k—~838Automated safety check: PassMIT
Create Pull Request with Work Item IDmakeplane/plane60k—~824Automated safety check: PassAGPL-3.0
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT

Similar skills

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Creating Description For Gh PR

    redis/jedis

    Official

    Generate a clear, concise GitHub PR title and description from the diff between two local git branches, and save it to prDescription.md in the repo root.

    12k GitHub stars~838 tokensUpdated today
    DevelopmentAuto-check passed

  • Create Pull Request with Work Item ID

    makeplane/plane

    Opens a pull request for the current branch using the repo's template, a work item ID in the title and a description filled in from the actual diff.

    60k GitHub stars~824 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Ansible Backport Creator

    ansible/ansible

    Creates backports of a merged Ansible devel pull request onto the right stable branches by cherry-picking its merge commit onto new backport branches.

    71k GitHub stars~1.2k tokensUpdated today
    DevelopmentAuto-check passed

More from pascalorg/editor

  • Furniture Fit Check

    pascalorg/editor

    Checks whether a sofa, table, bed or appliance fits in a measured Pascal room and reports only what the evidence supports, or asks for the missing measurements.

    25k GitHub stars~5.1k tokensUpdated today
    Auto-check passed

  • Pascal 3D Scene Editing

    pascalorg/editor

    Connects an agent to Pascal's MCP tools to create, inspect, edit, validate and save editable 3D building scenes, then return a verified editor link.

    25k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

  • Pascal Architecture PR Review

    pascalorg/editor

    Reviews a pull request against the Pascal editor's architectural rules: package boundaries, registry-driven node composition, hook hygiene and selector performance.

    25k GitHub stars~7.5k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Pascal Editor PR Opener

What does Pascal Editor PR Opener do?

Opens or refreshes a pull request on pascalorg/editor from the current branch, describing only what the branch's commits and diff actually contain. The agent first establishes what is really on the branch: it is not main, nothing uncommitted is left unexplained, and the PR covers only the branch's own commits and diff, not work that arrived by merging main, reverted commits or cherry-picks. If a file in the diff has no commit explaining it, the agent stops and asks.

When should I use Pascal Editor PR Opener?

Pascal Editor PR Opener fits situations like: opening a pull request from a finished branch in the editor repo; refreshing an existing PR's description after more commits; writing a how-to-test section that reviewers can follow.

How do I install Pascal Editor PR Opener in Claude Code?

Run `npx skills add pascalorg/editor --skill open-pr -a claude-code`. Or copy the skill folder (.agents/skills/open-pr in pascalorg/editor) into .claude/skills/open-pr in your project. Claude Code loads it when a task matches its description.

How do I install Pascal Editor PR Opener in Codex?

Run `npx skills add pascalorg/editor --skill open-pr -a codex`. Or copy the skill folder (.agents/skills/open-pr in pascalorg/editor) into .agents/skills/open-pr in your project. Codex loads it when a task matches its description.

Can I use Pascal Editor PR Opener in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pascalorg/editor --skill open-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/open-pr, .gemini/skills/open-pr, .github/skills/open-pr and .opencode/skills/open-pr in your project.

What does Pascal Editor PR Opener need to run?

Going by SKILL.md and its folder, Pascal Editor PR Opener needs the command-line tools its instructions call (git, gh and bun). Our summary lists: Git and the GitHub CLI (gh); Bun, for the bun run check-types check. Its frontmatter pre-approves these tools: Bash(git *), Bash(gh *), Read.

Does Pascal Editor PR Opener access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Pascal Editor PR Opener safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Pascal Editor PR Opener use?

Pascal Editor PR Opener is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Pascal Editor PR Opener use?

About 619 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Pascal Editor PR Opener?

Skills that share tags, products or a category with Pascal Editor PR Opener: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Creating Description For Gh PR (redis/jedis, 12k stars) and Create Pull Request with Work Item ID (makeplane/plane, 60k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pascal Editor PR Opener?

pascalorg (a GitHub organization) maintains it in pascalorg/editor, which has 24,695 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.

Source: pascalorg/editor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.