PR Review
Goal
Produce a maintainer-grade review that prioritizes correctness, regressions, missing tests, security concerns, docs drift, and release risk over style-only feedback.
When to use
- The user asks for a PR review, diff review, or merge readiness check.
- A branch or worktree needs review before merge.
- Agent-authored changes need an independent risk pass.
When not to use
- The user asks to implement fixes immediately; review only if requested.
- The change is only documentation; consider
docs-audit.
- The request is a whole-repo health review; use
repo-health-audit.
Inputs to inspect
- PR description, changed files, commits, and diff stats.
- Relevant source files, tests, docs, CI output, and release notes.
- Existing architecture or workflow docs that govern touched areas.
Review rubric
Check behavior changes, API contracts, data migrations, error handling, tests, docs, security-sensitive paths, dependencies, and deployment risk. Read references/review-rubric.md for detailed prompts and references/risk-table-template.md for report format.
Workflow
- Inspect diff stats and changed file names first.
- Identify user-visible behavior and contract changes.
- Read only the surrounding code needed to verify risk.
- Check tests and docs touched by the change.
- Run or report relevant validation if available.
- Lead with findings ordered by severity and include file/line evidence.
- Include a verdict only after findings.
Safety rules
- Do not approve, merge, push, or dismiss review comments unless explicitly authorized.
- Do not expose secrets from diffs, logs, or CI output.
- Separate confirmed findings from assumptions and coverage limits.
References
Read only when needed:
references/review-rubric.mdreferences/risk-table-template.md
Scripts
No bundled scripts.
Output format
Return:
- Verdict
- Blocking issues
- Non-blocking suggestions
- Test coverage
- Release risk
- Suggested review comments
Failure modes
- If line numbers are unavailable, reference file paths and nearby symbols.
- If validation cannot run, say what was skipped and why.
- If the diff is too large, review the riskiest areas first and state coverage limits.
Completion criteria
- Findings are concrete, reproducible, and tied to changed behavior.
- Severity order is clear.
- Test and release risks are explicit.
1---2name: pr-review3description: Review pull requests for correctness, maintainability, tests, security, docs impact, release risk, and agent-induced failure modes. Use when the user asks for a PR review, diff review, merge readiness check, or maintainer feedback.4license: Apache-2.05---67# PR Review89## Goal1011Produce a maintainer-grade review that prioritizes correctness, regressions, missing tests, security concerns, docs drift, and release risk over style-only feedback.1213## When to use1415- The user asks for a PR review, diff review, or merge readiness check.16- A branch or worktree needs review before merge.17- Agent-authored changes need an independent risk pass.1819## When not to use2021- The user asks to implement fixes immediately; review only if requested.22- The change is only documentation; consider `docs-audit`.23- The request is a whole-repo health review; use `repo-health-audit`.2425## Inputs to inspect2627- PR description, changed files, commits, and diff stats.28- Relevant source files, tests, docs, CI output, and release notes.29- Existing architecture or workflow docs that govern touched areas.3031## Review rubric3233Check behavior changes, API contracts, data migrations, error handling, tests, docs, security-sensitive paths, dependencies, and deployment risk. Read `references/review-rubric.md` for detailed prompts and `references/risk-table-template.md` for report format.3435## Workflow36371. Inspect diff stats and changed file names first.382. Identify user-visible behavior and contract changes.393. Read only the surrounding code needed to verify risk.404. Check tests and docs touched by the change.415. Run or report relevant validation if available.426. Lead with findings ordered by severity and include file/line evidence.437. Include a verdict only after findings.4445## Safety rules4647- Do not approve, merge, push, or dismiss review comments unless explicitly authorized.48- Do not expose secrets from diffs, logs, or CI output.49- Separate confirmed findings from assumptions and coverage limits.5051## References5253Read only when needed:5455- `references/review-rubric.md`56- `references/risk-table-template.md`5758## Scripts5960No bundled scripts.6162## Output format6364Return:65661. Verdict672. Blocking issues683. Non-blocking suggestions694. Test coverage705. Release risk716. Suggested review comments7273## Failure modes7475- If line numbers are unavailable, reference file paths and nearby symbols.76- If validation cannot run, say what was skipped and why.77- If the diff is too large, review the riskiest areas first and state coverage limits.7879## Completion criteria8081- Findings are concrete, reproducible, and tied to changed behavior.82- Severity order is clear.83- Test and release risks are explicit.
stark-ai-de