MANDATORY skill for ALL pull requests. An agent skill from ossappscollective/oss-weather.

MITAuto-check passedDevelopment

Install Open PR

skills CLI
$ npx skills add ossappscollective/oss-weather --skill open-pr -a claude-code

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

GitHub CLI
$ gh skill install ossappscollective/oss-weather 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/ossappscollective/oss-weather.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/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
456
Token cost
~918 tokens
SKILL.md length
495 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
MIT

At a glance

MANDATORY skill for ALL pull requests. An agent skill from ossappscollective/oss-weather.

  • Works in 4 steps: ALWAYS ensure the change was verified… → ALWAYS run git push and check for errors… → ALWAYS fix any errors — autofixup into… → …
  • Tasks that involve Pull requests
  • SKILL.md covers Mandatory Process, Writing the description, Default body (no PR template) and If a template ever gets added
  • Calls npx, yarn and git

What it does

Open PR is an agent skill from ossappscollective/oss-weather. MANDATORY skill for ALL pull requests. Must be used EVERY TIME before creating any pull request. No exceptions.

Its SKILL.md is about 920 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 Pull requests. It works with Android and iOS. The repository describes itself as: An OSS weather app for iOS/Android. The licence is MIT.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/open-pr”

Requirements

  • Node.js

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. ALWAYS ensure the change was verified before opening the PR. For logic changes this means the relevant Vitest tests pass (npx vitest run )…
  2. ALWAYS run git push and check for errors returned by any git hooks / CI (this repo has no local husky hooks, so commitlint runs in CI — a…
  3. ALWAYS fix any errors — autofixup into the relevant commits, or create a new commit if autofixup does not apply
  4. ALWAYS create the PR as draft

What it can do on your machine

Read from SKILL.md and the folder at commit 42715ad. 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:

    • npx
    • yarn
    • git
    • gh

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

  • Network

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

Open PR loads about 918 tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 495 words of instructions outside code blocks.

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

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 ossappscollective/oss-weather at commit 42715ad, republished under its MIT licence (© ossappscollective). 495 words, ~918 tokens.

Download SKILL.mdSave it as .claude/skills/open-pr/SKILL.md (or your agent's skills folder).
name
open-pr
description
MANDATORY skill for ALL pull requests. Must be used EVERY TIME before creating any pull request. No exceptions.

Generating Pull Requests

Mandatory Process

--auto (caller runs autonomously): skip step 0 sign-off and any push/PR approval wait — proceed directly. Still fix push-hook errors, still --draft.

  1. ALWAYS ensure the change was verified before opening the PR. For logic changes this means the relevant Vitest tests pass (npx vitest run <path>) and yarn svelte-check is clean; for UI/behavioral changes, confirm it by running the app (ns run ios / ns run android), or — when a native run isn't possible — flag that a visual check is still required. Propose the scenarios to verify.
  2. ALWAYS run git push and check for errors returned by any git hooks / CI (this repo has no local husky hooks, so commitlint runs in CI — a bad conventional-commit title/message will fail there, not on push)
  3. ALWAYS fix any errors — autofixup into the relevant commits, or create a new commit if autofixup does not apply
  4. ALWAYS create the PR as draft:
    1. This repo has no .github/PULL_REQUEST_TEMPLATE.md. Read it only if one exists and mirror its structure; otherwise write a clean default body (see "Writing the description" + "Default body" below).
    2. CRITICAL: --template and --body are mutually exclusive in gh pr create. Always use --body with an inline multiline string, never --template:
      sh
      gh pr create --draft --title "fix(camera): ..." --body "$(cat <<'EOF'
      ## Summary
      ...
      EOF
      )"
    3. ALWAYS use --draft — only the user decides when a PR is ready for review
    4. The PR title ALWAYS follows the Conventional Commits header (<type>(<scope>): <subject>) — same convention as the commit skill. The squash-merge uses this title as the changelog entry, so it must be a valid conventional commit
    5. ALWAYS reference the tracking issue in the body: Fixes #<issue> / Closes #<issue>
Show full SKILL.md (214 more words)Show less

Writing the description

The description is for a human reviewer who needs to grasp what this PR does at a glance. Write the kind of summary you'd write by hand.

  • Summarize the main changes only — the meaningful, functional changes a reviewer needs to know about. A few clear bullet points or short sentences is enough.
  • NEVER dump commit details — do not paste commit messages, do not write a commit-by-commit breakdown. The git history already holds that; repeating it just adds noise.
  • Skip non-important changes — small refactors, formatting, renames, lint fixes. They dilute the signal; leave them out.
  • If the description reads like a changelog of every diff, it's wrong. Clear, concise, high-level — that's the bar.

Default body (no PR template)

The repo has no PR template, so use this structure:

markdown
## Summary

<1-4 bullets of the meaningful changes>

## Testing

<what you ran / what still needs a manual visual check>

Fixes #<issue>

Keep it lean: ## Summary, an optional ## Testing, and the Fixes #<issue> line when an issue exists. Add a ## Breaking changes section only when the PR truly breaks something (impact + migration path).

If a template ever gets added

If .github/PULL_REQUEST_TEMPLATE.md exists, mirror its structure instead. The <!-- ... --> HTML comments in it are instructions to the author, not content — strip every one out; they must never appear in the final PR body. Check ([x]) only checklist boxes that genuinely hold; never check a box that isn't true.

© ossappscollective, 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 .claude/skills/open-pr of ossappscollective/oss-weather.

Open the folder on GitHubat commit 42715ad

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 skillossappscollective/oss-weather456—~918Automated safety check: PassMIT
Commit PRsamuelclay/NewsBlur7.6k—~4.1kAutomated safety check: PassMIT
PR Stackr0adkll/Campfire140—~1.7kAutomated safety check: PassGPL-3.0
Grix Code Reviewaskie/grix153—~799Automated safety check: PassCustom licence
Tlon Workflowtloncorp/tlon-apps107—~8.9kAutomated safety check: NotesMIT
PR Proofmrzmyr/pixy-mood-tracker-app154—~571Automated safety check: PassMIT

Similar skills

  • Commit PR

    samuelclay/NewsBlur

    A skill your agent uses when the user runs /commit-pr, says "commit and push", "open a PR", "ship this", asks to update an existing PR with new changes, or asks to resolve PR review comments in the…

    7.6k GitHub stars~4.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • PR Stack

    r0adkll/Campfire

    Open, describe, and maintain pull requests in Campfire, especially stacks of dependent PRs (each branch built on the one before).

    140 GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check passed
  • Audit Grix diffs and pull requests for correctness, regressions, security, lifecycle safety, and cross-component contract consistency.

    153 GitHub stars~799 tokensUpdated today
    DevelopmentAuto-check passed
  • Tlon Workflow

    tloncorp/tlon-apps

    A skill your agent uses when taking a Tlon Messenger task from a fresh worktree to a merged pull request: reproducing or fixing something in the iOS, Android or web app, validating it on a…

    107 GitHub stars~8.9k tokensUpdated today
    DevelopmentAuto-check: notes
  • PR Proof

    mrzmyr/pixy-mood-tracker-app

    Upload screenshots or videos to a PR body. An agent skill from mrzmyr/pixy-mood-tracker-app.

    154 GitHub stars~571 tokensUpdated today
    DevelopmentAuto-check passed
  • Nitro Sound Workflows

    hyochan/react-native-nitro-sound

    A skill your agent uses for react-native-nitro-sound repository work that should follow the project workflows for PR review, code audit, knowledge compilation, full verification, iOS or Android…

    961 GitHub stars~1.2k tokensUpdated 9 days ago
    MobileAuto-check passed

More from ossappscollective/oss-weather

All 8 skills in this repo
  • Commit

    ossappscollective/oss-weather

    MANDATORY skill for ALL commits. An agent skill from ossappscollective/oss-weather.

    456 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Feat

    ossappscollective/oss-weather

    Build a feature end-to-end (GitHub issue or free-text → plan → implement → PR), OR plan one read-only with --investigate.

    456 GitHub stars~3.9k tokensUpdated today
    Auto-check: warnings
  • Fix

    ossappscollective/oss-weather

    Debug and fix any non-trivial issue end-to-end, OR triage a GitHub bug issue read-only.

    456 GitHub stars~4.2k tokensUpdated today
    Auto-check: warnings
  • Investigate Contract

    ossappscollective/oss-weather

    Read-only guarantee + interactive-vs-autonomous (--auto) behavior for investigate modes.

    456 GitHub stars~803 tokensUpdated today
    Auto-check passed
  • Understand Project

    ossappscollective/oss-weather

    Ground a feature or fix in existing code before planning or building — find a similar pattern, identify reusable assets, map the touch surface.

    456 GitHub stars~576 tokensUpdated today
    Auto-check passed
  • Branch Check

    ossappscollective/oss-weather

    Ensure you're on a correct working branch off up-to-date main before planning or editing — starting from a GitHub issue when one is in play.

    456 GitHub stars~356 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Open PR

What does Open PR do?

MANDATORY skill for ALL pull requests. An agent skill from ossappscollective/oss-weather. Open PR is an agent skill from ossappscollective/oss-weather. MANDATORY skill for ALL pull requests.

When should I use Open PR?

Open PR fits situations like: tasks that involve Pull requests.

How do I install Open PR in Claude Code?

Run `npx skills add ossappscollective/oss-weather --skill open-pr -a claude-code`. Or copy the skill folder (.claude/skills/open-pr in ossappscollective/oss-weather) 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 ossappscollective/oss-weather --skill open-pr -a codex`. Or copy the skill folder (.claude/skills/open-pr in ossappscollective/oss-weather) 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 ossappscollective/oss-weather --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 (npx, yarn, git and gh). Our summary lists: Node.js.

Does Open PR access the network?

SKILL.md contains no URLs. Its commands use npx, git and gh, 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 918 tokens (SKILL.md is roughly 3.7k 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: Commit PR (samuelclay/NewsBlur, 7.6k stars), PR Stack (r0adkll/Campfire, 140 stars), Grix Code Review (askie/grix, 153 stars) and Tlon Workflow (tloncorp/tlon-apps, 107 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Open PR?

ossappscollective (a GitHub organization) maintains it in ossappscollective/oss-weather, which has 456 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 7, 2026.

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