pr-review

Automate four-perspective Freenet PR reviews from a PR number.

23|4|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/freenet/freenet-agent-skills --skill pr-review-freenet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/freenet/freenet-agent-skills/tree/main/skills/pr-review
Command: npx skills add https://github.com/freenet/freenet-agent-skills --skill pr-review-freenet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Freenet teams need consistent, high-quality PR reviews that cover multiple perspectives to catch issues early and reduce downstream defects.

Core Features & Use Cases

  • Four-perspective review workflow (code-first analysis, testing, skeptical review, big-picture assessment)
  • Structured guidance to identify gaps, risks, and anti-patterns in PRs
  • Suitable for maintainers, reviewers, and contributors aiming for robust code changes

Quick Start

Provide a PR number to initiate a full four-perspective review.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I automate multi-perspective PR reviews for Freenet?

Automate Freenet PR reviews by providing a PR number to trigger a four-perspective analysis covering code changes, tests, skeptical critique, and big-picture impact checks. The workflow outputs structured findings with recommended actions.

What is a four-perspective code review workflow?

A four-perspective code review analyzes pull requests across code-first changes, testing, skeptical review, and big-picture assessment. This multi-perspective approach identifies gaps, risks, and anti-patterns to ensure robust code changes.

Can I use this automated review for Freenet contributor pull requests?

Yes, this automated review suits Freenet maintainers, reviewers, and contributors. It applies to Freenet PRs to catch issues early and reduce downstream defects through structured quality-assurance checks.

What's the best way to run a skeptical critique on a pull request?

Run a skeptical critique by initiating the multi-perspective PR review with a PR number. The workflow includes a dedicated skeptical review perspective to surface anti-patterns and risks.

How do I get structured findings and recommended actions from a PR review?

Get structured findings by inputting a PR number into the review workflow. It outputs multi-perspective analysis results containing identified gaps, risks, and recommended actions for code changes.

Does this code review workflow require any dependencies?

No dependencies are required to run this PR review workflow. You simply provide a Freenet PR number to initiate the full four-perspective analysis and receive structured findings.