메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| 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"} |
Use this skill to produce a merge-readiness review, not a broad design memo.
reference/rubric.md only when you need the detailed severity rubric or checklist.Run toolbox/review-summary when you need the expected output sections without loading the reference file.
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.
Use when changing Maestro runtime, hosted runner, event contracts, migration packaging, or internal-to-public mirror behavior.
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.
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".
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.
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.
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.