pr-reviewer

Check CI evidence, linked issues, and PR hygiene before human review.

23|4|Updated May 7, 2025
One-click install
npx skills add https://github.com/Stack-and-Flow/design-system --skill pr-reviewer-stack-and-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-reviewer
Source: https://github.com/Stack-and-Flow/design-system/tree/main/.atl/skills/pr-reviewer
Command: npx skills add https://github.com/Stack-and-Flow/design-system --skill pr-reviewer-stack-and-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents weak or incomplete pull requests from reaching human reviewers by enforcing CI evidence, PR hygiene, component and visual audit checkpoints, and removal of transient review artifacts.

Core Features & Use Cases

  • Automated PR readiness gating: Verifies CI/build/test evidence, linked issue requirements, title/template hygiene, and scope clarity before any optional polish.
  • Component-quality compliance checks: Requires component-audit results for component changes and blocks drift from Storybook conventions and shared component contract rules.
  • Visual-review and artifact cleanup enforcement: Ensures visual/MCP-related requirements are satisfied and that Playwright/MCP runtime artifacts are removed before approval.

Quick Start

Use pr-reviewer right before you request human review so it can validate evidence, detect blockers, and return an APPROVED result when everything is ready.

Frequently Asked Questions about pr-reviewer

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

FAQPage Schema
How do I enforce CI evidence and PR hygiene checks before requesting human code review?

To automate a PR readiness gate, verify CI/build/test evidence, linked issue requirements, title and template hygiene, and review-scope clarity before requesting human review, blocking incomplete submissions.

What is a component audit for Storybook conventions and how does it work in pull requests?

A component audit verifies changed components against Storybook conventions, hook and component split compliance, and shared contract rules, requiring evidence before a pull request can be approved.

How do I check for forbidden TypeScript patterns and hook compliance in a code review?

Deterministic checks scan for forbidden TypeScript patterns and enforce hook/component split compliance, blocking pull requests that violate these rules before they reach a human reviewer for final approval.

Do I need to remove Playwright and MCP runtime artifacts before a pull request can be approved?

Yes, mandatory cleanup of MCP artifacts and Playwright runtime artifacts is required before approval, ensuring visual-review requirements are satisfied and no transient review artifacts remain in the submission.

Can I use automated visual review checks for Storybook story play function placement?

Yes, automated visual review checks can enforce story play function placement and verify Storybook conventions, ensuring component changes meet visual and MCP artifact requirements before producing an approval verdict.

What are the limitations of automated PR readiness gating for component changes?

Automated PR readiness gating requires deterministic checks to pass completely, meaning any missing component-audit evidence, failed CI build evidence, or uncleared MCP artifacts will block the pull request from approval.