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

Open PR

by analogjs in analogjs/analog

Commit the current work, push the current feature branch, and open a GitHub PR filled out from the repo's PR template.

MITAuto-check passedDevelopment

Install Open PR

skills CLI
$ npx skills add analogjs/analog --skill open-pr -a claude-code

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

GitHub CLI
$ gh skill install analogjs/analog 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/analogjs/analog.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
3.2k
Token cost
~944 tokens
SKILL.md length
502 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Commit the current work, push the current feature branch, and open a GitHub PR filled out from the repo's PR template.

  • Works in 5 steps: Assess the working tree → Guard the branch — don't commit to base → Format, then commit → …
  • The user says open a PR
  • SKILL.md covers 1. Assess the working tree, 2. Guard the branch — don't…, 3. Format, then commit and 4. Push, plus 2 more sections
  • Calls git, gh and npx

What it does

Open PR is an agent skill from analogjs/analog. Commit the current work, push the current feature branch, and open a GitHub PR filled out from the repo's PR template. Defaults the base branch to beta. Assumes you're already on a feature branch — it does not create branches. Use when the user says "open a PR", "create a PR", "make a PR", or asks to submit the current changes for review.

Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git workflow and Pull requests. It works with GitHub, Git and Prettier. The repository describes itself as: The fullstack meta-framework for Angular. Powered by Vite and Nitro. The licence is MIT.

When your agent uses it

  • The user says open a PR
  • Asks to submit the current changes for review

Example prompts

  • “s PR template. Defaults the base branch to beta. Assumes you”
  • “open a PR”
  • “create a PR”
  • “/open-pr”

Requirements

  • Node.js

Workflow steps

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

  1. Assess the working tree
  2. Guard the branch — don't commit to base
  3. Format, then commit
  4. Push
  5. Open the PR

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh
    • npx

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

  • Network

    No URLs in SKILL.md. Its commands use git, gh and npx, 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

Open PR loads about 944 tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 502 words of instructions outside code blocks.

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

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 analogjs/analog at commit eedd920, republished under its MIT licence (© analogjs). 502 words, ~944 tokens.

Download SKILL.mdSave it as .claude/skills/open-pr/SKILL.md (or your agent's skills folder).
name
open-pr
description
Commit the current work, push the current feature branch, and open a GitHub PR filled out from the repo's PR template. Defaults the base branch to `beta`. Assumes you're already on a feature branch — it does not create branches. Use when the user says "open a PR", "create a PR", "make a PR", or asks to submit the current changes for review.

Take the current working changes and turn them into a GitHub pull request: commit, format, push, and open the PR with gh, filling out the repository's PR template.

This skill prepares and opens the PR only. It does not create branches and does not write code. It assumes you are already on the feature branch you want to submit. Default the base branch to beta; if the user names a different base (e.g. "PR to main"), use that instead.

1. Assess the working tree

  • git status, git diff, and git diff --cached to see what's staged/unstaged.
  • git branch --show-current for the current branch.
  • If there's nothing to commit and the branch is already pushed, skip to step 4 (just open the PR for existing commits).

2. Guard the branch — don't commit to base

  • If the current branch is the base branch (beta, or whatever the user chose), stop and tell the user: you're on the base branch and this skill doesn't branch. Ask them to switch to a feature branch first (the fix-issue / feature flow owns branch creation).
  • Otherwise proceed on the current feature branch.

3. Format, then commit

  • Run prettier on the changed files before committing so the commit is clean: npx prettier --write <changed files> then npx prettier --check <changed files>. (Prefer the repo's own prettier if installed; fall back to npx when deps aren't installed.)

  • Stage the intended files explicitly (git add <paths>) — don't blindly git add -A.

  • Write a conventional commit message: <type>(<scope>): <summary>, with a body explaining the why, and Closes #<issue> if one applies.

  • Do not add co-author trailers or generated-by attribution to commits or PR descriptions.

  • If commits already exist and there's nothing new to add, skip committing.

4. Push

  • git push -u origin <branch> (use --force-with-lease, never --force, if amending an already-pushed branch).
Show full SKILL.md (215 more words)Show less

5. Open the PR

  • Read the repo's PR template if present: .github/PULL_REQUEST_TEMPLATE.md (or .github/pull_request_template.md). Fill out every section — don't submit a bare body.

  • Determine the affected scope for templates that ask for it: map changed file paths against .github/pr-scope-map.json (or CONTRIBUTING.md) when those exist; otherwise infer the primary package/area from the paths.

  • Default the merge-strategy checkbox to Squash merge unless the user says otherwise.

  • For the test-plan checklist: only check boxes for steps you actually ran. If dependencies weren't installed and you couldn't run the suite, leave those unchecked and add a short note saying CI/maintainer will verify — don't claim tests passed when they didn't.

  • Create the PR with the base defaulting to beta:

    gh pr create --base beta --title "<conventional title>" --body "$(cat <<'EOF'
<filled-out template>
EOF
)"

  • Opening a PR is an outward-facing action. If the user hasn't clearly authorized it this turn, confirm the title and base branch before running gh pr create. Report the resulting PR URL.

Notes

  • Use the gh CLI for all GitHub operations; interactive git flags (-i) are unavailable.
  • If gh pr create reports a PR already exists for the branch, surface that URL instead of erroring out.
  • Keep the PR scoped to the work at hand — flag (don't silently include) unrelated changes you notice in the working tree.

© analogjs, 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 analogjs/analog.

Open the folder on GitHubat commit eedd920

Compare with similar skills

Open PR 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.

Open PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Open PR this skillanalogjs/analog3.2k—~944Automated 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 yesterday
    DevelopmentAuto-check passed

  • Pascal Editor PR Opener

    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.

    25k GitHub stars~619 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from analogjs/analog

  • Analogjs

    analogjs/analog

    Conventions for working in an AnalogJS app (an Angular meta-framework powered by Vite) — file-based routing with .page.ts files, RouteMeta, server and API routes on Nitro/h3, page load functions and…

    3.2k GitHub stars~891 tokensUpdated yesterday
    Auto-check passed

  • Fix Issue

    analogjs/analog

    End-to-end flow for resolving a GitHub issue — fetch and understand the issue, create a feature branch off beta, implement and verify the fix, then hand off to the open-pr skill.

    3.2k GitHub stars~808 tokensUpdated yesterday
    Auto-check passed

  • Handhold PR

    analogjs/analog

    Watch a PR's CI, diagnose every failing check, fix what's actually broken, resolve CodeRabbit's major findings, and keep iterating until the PR is green.

    3.2k GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed

  • Investigate Issue

    analogjs/analog

    Investigate a GitHub issue end to end — reproduce the reporter's repo or code snippet in an isolated sandbox outside the monorepo, trace the root cause in the source, and draft a reply back to the…

    3.2k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Open PR

What does Open PR do?

Commit the current work, push the current feature branch, and open a GitHub PR filled out from the repo's PR template. Open PR is an agent skill from analogjs/analog. Commit the current work, push the current feature branch, and open a GitHub PR filled out from the repo's PR template.

When should I use Open PR?

Open PR fits situations like: the user says open a PR; asks to submit the current changes for review.

How do I install Open PR in Claude Code?

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

How do I install Open PR in Codex?

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

Can I use Open PR 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 analogjs/analog --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 Open PR need to run?

Going by SKILL.md and its folder, Open PR needs the command-line tools its instructions call (git, gh and npx). Our summary lists: Node.js.

Does Open PR access the network?

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

Is Open PR 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 Open PR use?

Open PR 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 Open PR use?

About 944 tokens (SKILL.md is roughly 3.8k 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 Open PR?

Skills that share tags, products or a category with Open PR: 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 Open PR?

analogjs (a GitHub organization) maintains it in analogjs/analog, which has 3,187 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 7, 2026.

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