pr-review

Review pull requests with a security-first checklist for secret leakage and supply-chain risks.

3|2|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/Paxeer-Network/Sidiora-Perpetual-Protocol --skill pr-review-paxeer-network
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/Paxeer-Network/Sidiora-Perpetual-Protocol/tree/main/.windsurf/skills/pr-review
Command: npx skills add https://github.com/Paxeer-Network/Sidiora-Perpetual-Protocol --skill pr-review-paxeer-network

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of conducting thorough and security-focused reviews of code changes in pull requests, ensuring code quality and mitigating risks.

Core Features & Use Cases

  • Security-First Checklist: Guides reviewers through critical security checks, including secret leakage, supply-chain risks, and cross-platform vulnerabilities.
  • Structured Analysis: Enforces a systematic file-by-file analysis and architectural overview.
  • Use Case: When a developer submits a PR that updates dependencies or modifies authentication logic, this Skill provides a checklist to ensure no security vulnerabilities are introduced.

Quick Start

Use the pr-review skill to analyze the changes in the current pull request.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I review a pull request for security vulnerabilities and dependency risks?

Reviewing a pull request for security vulnerabilities requires a security-first checklist that systematically analyzes file changes to detect secret leakage, supply-chain risks from dependency updates, and cross-platform architecture flaws.

What does a supply chain risk audit involve when updating npm dependencies in a PR?

A supply chain risk audit for dependency updates involves analyzing the pull request file changes to identify vulnerable packages, detect malicious injections, and ensure that new dependencies do not introduce hidden security backdoors.

How can I check for secret leakage in code changes before merging a pull request?

Checking for secret leakage in code changes involves applying a structured file-by-file analysis during the PR review to ensure that hardcoded credentials, API keys, and sensitive tokens are not accidentally committed.

How do I evaluate React performance impacts when reviewing pull requests?

Evaluating React performance impacts during PR review requires analyzing the modified component architecture and rendering logic to ensure that code changes do not introduce unnecessary re-renders or degrade application speed.

Does this PR review process work for cross-platform architecture changes?

Yes, the PR review process enforces architectural visualization and systematic file analysis specifically designed to identify cross-platform vulnerabilities and architectural flaws in code changes across different platforms.

How do I enforce a structured file analysis workflow for pull request reviews?

Enforcing a structured file analysis workflow involves applying a comprehensive checklist that guides reviewers through a systematic file-by-file analysis and architectural overview to ensure code quality and mitigate risks.