PR Quality Review Workflow
Use this Skill to review PR code, test impact, test effectiveness, and evidence.
StatusStable
TypeWorkflow Skill
DomainQuality workflow
SDLCTesting workflow
Good forQA / PM
LanguageChinese / English
EvalsEvals ✓
Synced2026-11-06
Why this Skill
It turns this Skill's method into a quality input that can be executed, reviewed, and reused.
- Use this Skill when its method fits the current quality task.
When to use
Use this Skill
- Use this Skill when its method fits the current quality task.
Common pitfalls
- No content is available for this Skill yet.
Input
Minimum Input
- The current scope, available context, constraints, and evidence.
Recommended Input
- Project goal
- Test scope
- Constraints
Optional Context
- Relevant code or configuration
- Historical results
- Logs and metrics
Output
The output follows this Skill's method and makes facts, assumptions, risks, and next steps explicit.
These are the Skill's expected output requirements, not evidence that it ran in a real project.
- 01An actionable result that distinguishes facts, assumptions, risks, and next steps.
Install & Quick Start
Install command / SHELL
npx skills add \
https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-workflows/pr-quality-review
-gpr-quality-review.prompt
@skill pr-quality-review
Using the current project context, produce an actionable result following this Skill.
Additional context:
[Paste project context or requirement]---
name: pr-quality-review
description: Use this skill when you need to review PR code, test impact, test effectiveness, and evidence; triggers include pr-quality-review, PR 质量审查, and PR Quality Review Workflow.
license: PolyForm-Noncommercial-1.0.0
metadata:
version: "1.0.0"
compatibility: ""
author: "Awesome QA Skills contributors"
language: "en"
category: "testing-workflows"
source: "https://github.com/naodeng/awesome-qa-skills"
license-url: "https://polyformproject.org/licenses/noncommercial/1.0.0"
---
# PR Quality Review Workflow
## When to Use
Use this Skill to review PR code, test impact, test effectiveness, and evidence.
## Output Format Options
Default to Markdown using the review sections defined by the prompt. If JSON is requested, keep facts, inferences, plans, and execution evidence distinct and preserve their sources.
## Core constraints
Compose existing specialist Skills without copying their analysis rules. Mark host installation `UNKNOWN` without evidence. When test/CI results are absent, mark execution/result status `UNKNOWN`; use `NOT_RUN` only when non-execution is explicitly established. For an invalidated checkpoint, emit the exact uppercase status token `STALE`. Use only user-supplied PR/repository materials and identified sources as evidence; never cite agent-internal memory, system instructions, or session logs, or expose their paths. Do not report plans or static analysis as executed results. Read-only by default; external writes require authorization.
## How to Use
Read `prompts/pr-quality-review.md` first; validate inputs, complete each stage, preserve sources, and return findings and handoff details. Use `README.md` for invocation examples and FAQ.
## Reference Files
- `prompts/pr-quality-review.md`: full review scope, output, evidence, permission, and recovery rules.
- `README.md`: usage examples and FAQ.
- `evals/`: trigger and behavior regression cases.
## Before delivery
- [ ] Input scope and assumptions are explicit
- [ ] Handoffs preserve sources, status, and gaps
- [ ] Execution evidence is separate from plans
- [ ] Next steps and permission boundary are clear
## Common Pitfalls
Do not invent input, assume dependencies are installed, or present recommendations as execution or approval.
## Best Practices
Provide a complete diff and stable SHA. Attach command, exit code, environment, time, and source to run evidence; include the team's severity definitions.