What is release-pr-review?

A review procedure for an open release pull request, which is a proposed set of code changes awaiting approval before a release. It checks the release branch, reviews the changes for correctness and simplicity, and verifies automated review comments.

Use it to review gated release pull requests, inspect their commit range, check the changelog, and apply necessary fixes before publishing.

It adds a controlled review step before release changes are merged into the main branch. It stops when the branch, pull request, or release conditions do not match the expected setup.

release-pr-review — Skill for Claude Code by cyanheads

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add cyanheads/open-meteo-mcp-server --skill release-pr-review

Clone the repo

git clone --depth 1 https://github.com/cyanheads/open-meteo-mcp-server

Made for: Claude Code.

Or install open-meteo-mcp-server, the plugin that ships this one along with the rest of its 33 skills, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cyanheads/open-meteo-mcp-server/release-pr-review/github.svg)](https://agentmods.dev/skills/cyanheads/open-meteo-mcp-server/release-pr-review)

Your own site

<a href="https://agentmods.dev/skills/cyanheads/open-meteo-mcp-server/release-pr-review"><img src="https://agentmods.dev/badge/skills/cyanheads/open-meteo-mcp-server/release-pr-review/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/cyanheads/open-meteo-mcp-server/release-pr-review"><img src="https://agentmods.dev/badge/skills/cyanheads/open-meteo-mcp-server/release-pr-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 139 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,634 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00139	$0.02634
Opus 5	$0.00069	$0.01317
Sonnet 5	$0.00028	$0.00527
Haiku 4.5	$0.00014	$0.00263

Measured yesterday against content hash 4fb10c42f4e1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

release-pr-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to release-pr-review — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/release-pr-review/SKILL.md · 148 lines

How it starts

The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.

When to use

git-wrapup has halted at an open release PR (gated mode) and the caller wants the release reviewed before it ships. The PR is the review target: the stack is committed, the tree is clean, gates were green when the PR opened.

Not for: PRs from outside contributors (those get a human reply, not an autosquash), non-release branches, or a PR that has already merged.

Preconditions

The repo is checked out on release/<version> with a clean working tree
The PR is open, and its head SHA equals local HEAD
No tag v<version> exists yet — tagging is release-and-publish's job, after this pass

Verify all three in step 1; halt on any mismatch.

Steps

1. Orient

git branch --show-current                                   # release/<version>
git status --short                                          # empty
gh pr view --json number,state,title,body,headRefOid,baseRefName  # state OPEN, base main, headRefOid == git rev-parse HEAD
git log --oneline main..HEAD                                # the stack: work commits, release commit on top
git diff main...HEAD --stat

Read skills/code-simplifier/SKILL.md in full. Read the changelog entry for this version (changelog/<major.minor>.x/<version>.md) — it is the claim the diff has to back.

2. Establish the review range

The range is main...HEAD — every commit in the PR. code-simplifier's Phase 1 looks at the uncommitted diff and, finding none, falls back to the last commit; override that here: the diff under review is git diff main...HEAD, and new files are the ones git diff main...HEAD --name-status marks A. Everything else in the simplifier procedure applies as written: read the full files, survey adjacent code, run the project gate once for a baseline.

3. Review

Two lenses over the range. Skip a dimension that does not apply; do not run any of this as ceremony.

Simplifier lens — code-simplifier Phase 3 verbatim: cohesion, quality, efficiency, and the framework-specific rules.

Read the full file on GitHub · 148 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 148 lines · 139 tokens per session scan A 4fb10c42f4e1

Subscribe to this mod's changes

release-pr-review is a skill published in the GitHub repository cyanheads/open-meteo-mcp-server (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 139 tokens to every session and 2,634 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to release-pr-review, differing in 0 lines, and is treated as a copy.

Code review Git and workflow Releases ai-agents ai-tools climate cyanheads forecast mcp