pr-review-guard

Applies a four-gate checklist to review pull requests before merge.

1|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/psiagoleal/ai-coding-agent-profiles --skill pr-review-guard-psiagoleal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review-guard
Source: https://github.com/psiagoleal/ai-coding-agent-profiles/tree/main/skills/pr-review-guard
Command: npx skills add https://github.com/psiagoleal/ai-coding-agent-profiles --skill pr-review-guard-psiagoleal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated code often completes 80% of a requirement while hiding the remaining 20% of defects: compilation failures, unhandled exceptions, regressions, and OWASP vulnerabilities. This Skill structures the review of AI-generated diffs so hidden defects are caught by the cheapest possible gate before human judgment is spent. ## Core Features & Use Cases - Ordered four-gate checklist: static checks (build, lint, types), test suite, security scanning (secrets, injection, SAST/SCA), then human or clean-context agent judgment, always in ascending cost order. - Provenance and audit rules: AI usage is recorded only in the commit message between braces, with no agent attribution in PR descriptions, code comments, ADRs, or Co-authored-by trailers. - Review summary output: produces a checklist report with residual risks and an explicit recommendation (approve, approve with reservations, or block), always requiring human validation before merge. - Use Case: Before approving a PR containing an agent-generated diff, run the checklist to confirm the build passes, tests cover the changed behavior, no secrets or injection vectors exist, and the diff scope matches the request. ## Quick Start Review this pull request diff using the pr-review-guard checklist and give me a recommendation before I merge.

Frequently Asked Questions about pr-review-guard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review AI-generated code before merging a pull request?▼

Run a four-gate checklist in ascending cost order: static checks (build, lint, types), the declared test suite, security scanning for secrets and injection, then human or clean-context agent judgment. Never open the judgment gate before the first three pass.

What is the correct order for code review gates?▼

Order gates by cost: static analysis first (milliseconds), tests second (seconds), security scanning third (seconds), and human judgment last. A cheap gate that fails saves an entire round of the expensive gate that would find the same defect later.

Can an AI agent review its own generated code?▼

An agent reviewer must run in a clean context, receiving only the contract and the executed artifact, never the implementer's reasoning. A verifier that read the author's justification tends to validate it, so the author cannot judge its own work.

How should AI usage be recorded in commits and pull requests?▼

Record AI usage only in the commit message between braces, such as {agent: name; model: version}. PR descriptions, code comments, ADRs, and Co-authored-by or Assisted-by trailers must never mention AI usage or attribute authorship to an agent.

Why is a flaky CI gate worse than no gate at all?▼

A gate that fails intermittently teaches the team to re-run until it passes, after which it filters nothing and only adds latency. Instability in a gate is a defect to fix, not noise to tolerate.