pac-review

Standardize code-change reviews with structured findings and human-review callouts.

2|1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/ladislas/mypac --skill pac-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pac-review
Source: https://github.com/ladislas/mypac/tree/main/skills/pac-review
Command: npx skills add https://github.com/ladislas/mypac --skill pac-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a standardized framework for reviewing code changes, ensuring consistent, thorough critiques across teams and projects.

Core Features & Use Cases

  • Establishes a repeatable review workflow with clear flagging criteria and actionable feedback.
  • Guides reviewers through diffs, pull requests, branch comparisons, and commits to surface high-impact issues.
  • Enforces structured findings with a mandatory "Human Reviewer Callouts" section to communicate non-blocking risks.

Quick Start

Apply these guidelines to a given code change to produce a structured, actionable review summary.

Frequently Asked Questions about pac-review

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

FAQPage Schema
How do I standardize code reviews for pull requests?

You can standardize code reviews for pull requests by applying a repeatable workflow with clear flagging criteria and actionable feedback to ensure consistency across teams.

What is a structured code review workflow?

A structured code review workflow guides reviewers through diffs and commits to surface high-impact issues, enforcing structured findings and mandatory human-review callouts for non-blocking risks.

Can I review uncommitted git changes using a standardized framework?

Yes, you can apply standardized review guidelines to uncommitted git changes, branch comparisons, and specific commits to produce a structured, actionable review summary.

What's the best way to flag non-blocking risks during a code review?

The best way to flag non-blocking risks during a code review is to enforce a mandatory Human Reviewer Callouts section that clearly communicates these risks without blocking the merge.

Does a structured review process work for branch comparisons?

Yes, a structured review process applies directly to branch comparisons, guiding reviewers through the diff to surface high-impact issues and generate actionable feedback.

How to ensure consistency and thoroughness in code change reviews?

To ensure consistency and thoroughness in code change reviews, apply a standardized framework that enforces clear flagging, structured findings, and mandatory human-review callouts.