How do I install the Pr Review skill?

Run npx skillmds@latest add tomevault-io/pr-review-2 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.

What does the Pr Review skill do?

Review a Pull Request for code quality, tests, and merge readiness. Use when reviewing PRs, checking for merge conflicts, or providing feedback before merging. Use when this capability is needed. It is listed under AI & ML on SkillMD.

Is Pr Review safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. 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?

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

Pr Review by tomevault-io — Agent Skill

Name: Pr Review
Author: tomevault-io

File contents

PR Review

Review this Pull Request:

This skill is for review-only work. Prefer gh pr checkout <number> --detach so disposable local branches do not accumulate.

Analyze the quality of the code, the tests and the overall change. Check for merge conflicts with main, advise on fixes if a conflict exists.

Prioritize findings:

Correctness bugs and behavior regressions
Missing or weak regression coverage for the changed behavior
Merge conflicts or dirty merge state against main
Failing or missing GitHub CI context

When the review is complete, update the PR review-state label on GitHub:

Apply ready_to_merge and remove needs_work when there are no blocking findings, the PR is merge-clean, and GitHub CI is green
Apply needs_work and remove ready_to_merge when blocking findings remain, coverage is insufficient for the risk, merge conflicts exist, or GitHub CI is failing

Use:

gh pr edit <number> --add-label ready_to_merge --remove-label needs_work
gh pr edit <number> --add-label needs_work --remove-label ready_to_merge

Give me feedback on the PR and whether it is ready to merge.

If asked to give feedback on the PR, do so with a terse response in a encouraging, warm and friendly tone. Be appreciative of the work and the effort put into the PR.

Source: agentjido/req_llm — distributed by TomeVault.

Frequently asked questions

Pr Review