Run any Skill in Manus with one click

pr-review

Stars1

Forks1

UpdatedMay 16, 2026 at 07:14

Review GitHub pull requests for correctness, regressions, missing tests, and merge readiness. Use when the user asks for PR review, review feedback, or a pre-merge risk pass.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

evalops

evalops/maestro

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

5 files

SKILL.md

readonly

name	pr-review
description	Review GitHub pull requests for correctness, regressions, missing tests, and merge readiness. Use when the user asks for PR review, review feedback, or a pre-merge risk pass.
license	Complete terms in LICENSE.txt
compatibility	Maestro skill packages with bounded GitHub MCP tools and executable toolbox entries.
allowed-tools	["read","search","bash"]
builtin-tools	["read","search"]
mode	review
isolatedContext	true
metadata	{"version":"0.1.0","category":"evalops-operations","artifactSchema":"evalops.maestro.skill.pr_review.v1"}

PR Review

Use this skill to produce a merge-readiness review, not a broad design memo.

Workflow

Identify the PR, base branch, changed files, linked issue, CI status, and review history.
Load reference/rubric.md only when you need the detailed severity rubric or checklist.
Inspect the changed code and nearby tests. Prefer local repo reads for code and bounded GitHub MCP calls for PR metadata.
Lead with findings ordered by severity. Include file and line when the issue is in code.
Call out missing tests only when they hide real risk.
If no issues are found, say that clearly and name the remaining residual risk.

Toolbox

Run toolbox/review-summary when you need the expected output sections without loading the reference file.

MCP Scope

The bundled GitHub MCP config exposes only pull-request, review, file, and check metadata needed for review. Do not ask it for broad organization scans from this skill.

More from this repository

same repository

maestro-mirror-and-runtime-pr

evalops/maestro

Use when changing Maestro runtime, hosted runner, event contracts, migration packaging, or internal-to-public mirror behavior.

2026-07-231

incident-triage

evalops/maestro

Triage production incidents by building a timeline, scoping blast radius, identifying mitigations, and preserving evidence. Use when the user asks about an outage, regression, alert, Sentry issue, or incident follow-up.

2026-07-201

install-code-review

evalops/maestro

Install automated Maestro code review in a GitHub repository's CI — add a pull_request workflow that runs `maestro exec` and posts a merge-readiness review as a PR comment. Use when the user wants to set up automated PR review, wire Maestro into CI/CD, or "install code review".

2026-07-131

security-review

evalops/maestro

Correctness-first, depth-first security audit of a single repository using STRIDE, OWASP Top 10, the OWASP LLM Top 10, and supply-chain analysis. Use when the user asks for a security review, a vulnerability audit, a threat model, or a pre-release security pass.

2026-07-131

release-verification

evalops/maestro

Verify release readiness and post-release health from PRs, CI, tags, deploy evidence, rollback notes, and operator artifacts. Use when the user asks whether a release can ship, has shipped, or is safe to promote.

2026-05-161

doc-coauthoring

evalops/maestro

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

2026-04-151

name	pr-review
description	Review GitHub pull requests for correctness, regressions, missing tests, and merge readiness. Use when the user asks for PR review, review feedback, or a pre-merge risk pass.
license	Complete terms in LICENSE.txt
compatibility	Maestro skill packages with bounded GitHub MCP tools and executable toolbox entries.
allowed-tools	["read","search","bash"]
builtin-tools	["read","search"]
mode	review
isolatedContext	true
metadata	{"version":"0.1.0","category":"evalops-operations","artifactSchema":"evalops.maestro.skill.pr_review.v1"}

PR Review

Use this skill to produce a merge-readiness review, not a broad design memo.

Workflow

Identify the PR, base branch, changed files, linked issue, CI status, and review history.
Load reference/rubric.md only when you need the detailed severity rubric or checklist.
Inspect the changed code and nearby tests. Prefer local repo reads for code and bounded GitHub MCP calls for PR metadata.
Lead with findings ordered by severity. Include file and line when the issue is in code.
Call out missing tests only when they hide real risk.
If no issues are found, say that clearly and name the remaining residual risk.

Toolbox

Run toolbox/review-summary when you need the expected output sections without loading the reference file.

MCP Scope

The bundled GitHub MCP config exposes only pull-request, review, file, and check metadata needed for review. Do not ask it for broad organization scans from this skill.