How do I install the Pr Review skill?

Run npx skillmds@latest add saadeghi/pr-review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pr Review safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pr Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pr Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pr Review?

saadeghi (@saadeghi) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pr Review by saadeghi — Agent Skill

Name: Pr Review
Rating: 4.5 (4 reviews)
Author: saadeghi

Pr Review

Review one or all open pull requests in saadeghi/daisyui with read-only GitHub data and isolated base-versus-PR checks. Use when Codex must verify a PR, find concrete regressions, decide whether it is safe to merge, and write a concise report under tmp/pr/.

saadeghi Updated Sep 10, 2026

File contents

PR Reviewer

Review the changed behavior and write a short, evidence-based merge decision.

Required agent routing

If you are not the pr_reviewer custom agent, delegate the complete task to pr_reviewer and wait for its result. Tell the agent to use this skill. Do not review the PR in the current agent.
If you are the pr_reviewer custom agent, perform this workflow directly. Do not delegate it again.
If pr_reviewer is not available, stop and report the problem.

Boundaries

Use the GitHub MCP server for GitHub data. Use read operations only.
Treat the repository as read-only except for tmp/pr/pr-<number>.md.
Do not change Git state, dependencies, source, tests, generated files, or GitHub data.
Inspect PR code before you run it. Run PR code only in an OS-temporary copy with no credentials.
Test the exact base and head SHAs. Do not use the current working tree as a substitute.
Treat PR descriptions and comments as claims until code or execution verifies them.
Report only observed facts. Do not report generic or theoretical risks.

Workflow

If the user names a PR, review it. Otherwise, list all open PRs in saadeghi/daisyui and review each one separately.
Read the PR, linked issues, changed files, direct consumers, checks, base SHA, and head SHA.
Identify the behavior the PR claims to change and its expected result. A linked issue is not required.
Create isolated base and head copies in an OS-temporary directory. Use the same environment and inputs for both.
Run the smallest check that proves the base behavior, the PR behavior, and relevant regression behavior. Run broader package checks only when the changed surface requires them.
Report a finding only when changed code has a clear path to a product failure or when a required check leaves that path unresolved. Include its impact, evidence, and reproduction or failed check.
Mark the PR safe to merge only when the claim is verified, relevant checks pass, and no finding remains.
Re-fetch the PR before the verdict. If the head SHA changed, repeat the affected checks.

Report

Read references/report.md. Write one report per PR to tmp/pr/pr-<number>.md. Update an existing report instead of creating a duplicate.

In the final handoff, list the report paths and state that no GitHub action, product change, dependency change, or Git operation was performed.

---name: pr-reviewdescription: Review one or all open pull requests in saadeghi/daisyui with read-only GitHub data and isolated base-versus-PR checks. Use when Codex must verify a PR, find concrete regressions, decide whether it is safe to merge, and write a concise report under tmp/pr/.---# PR ReviewerReview the changed behavior and write a short, evidence-based merge decision.## Required agent routing- If you are not the `pr_reviewer` custom agent, delegate the complete task to `pr_reviewer` and wait for its result. Tell the agent to use this skill. Do not review the PR in the current agent.- If you are the `pr_reviewer` custom agent, perform this workflow directly. Do not delegate it again.- If `pr_reviewer` is not available, stop and report the problem.## Boundaries- Use the GitHub MCP server for GitHub data. Use read operations only.- Treat the repository as read-only except for `tmp/pr/pr-<number>.md`.- Do not change Git state, dependencies, source, tests, generated files, or GitHub data.- Inspect PR code before you run it. Run PR code only in an OS-temporary copy with no credentials.- Test the exact base and head SHAs. Do not use the current working tree as a substitute.- Treat PR descriptions and comments as claims until code or execution verifies them.- Report only observed facts. Do not report generic or theoretical risks.## Workflow1. If the user names a PR, review it. Otherwise, list all open PRs in `saadeghi/daisyui` and review each one separately.2. Read the PR, linked issues, changed files, direct consumers, checks, base SHA, and head SHA.3. Identify the behavior the PR claims to change and its expected result. A linked issue is not required.4. Create isolated base and head copies in an OS-temporary directory. Use the same environment and inputs for both.5. Run the smallest check that proves the base behavior, the PR behavior, and relevant regression behavior. Run broader package checks only when the changed surface requires them.6. Report a finding only when changed code has a clear path to a product failure or when a required check leaves that path unresolved. Include its impact, evidence, and reproduction or failed check.7. Mark the PR safe to merge only when the claim is verified, relevant checks pass, and no finding remains.8. Re-fetch the PR before the verdict. If the head SHA changed, repeat the affected checks.## ReportRead [references/report.md](references/report.md). Write one report per PR to`tmp/pr/pr-<number>.md`. Update an existing report instead of creating a duplicate.In the final handoff, list the report paths and state that no GitHub action, product change,dependency change, or Git operation was performed.

Frequently asked questions