# Pr Review Workflow

> Use when reviewing a pull request, diff, branch, or code change for bugs, regressions, missing tests, and release risk.

- Skill: `memoash/pr-review-workflow` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add memoash/pr-review-workflow`
- Raw SKILL.md: https://api.skillmd.com/api/skills/memoash/pr-review-workflow/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: MemoAsh (https://skillmd.com/u/memoash)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/memoash/pr-review-workflow

---


# PR Review Workflow

## Goal

Find the highest-impact issues in the change. The output is for an engineer deciding whether the PR can merge.

## Process

1. Read the diff and the surrounding code needed to understand behavior.
2. Identify changed contracts, data flow, error handling, user-visible behavior, and tests.
3. List findings first, ordered by severity.
4. Keep summaries brief.

## Finding Rules

- A finding must describe a concrete risk.
- A finding must include file and line evidence.
- Do not include speculative issues without stating the assumption.
- Do not include style-only comments.
- If there are no issues, say that clearly and mention residual test risk.

## Output Format

Use `templates/review-output.md`.

End with `templates/completion-receipt.md`. The receipt must separate checked claims from unverified claims.

## Verification

Before finishing, apply `verification.md`.