review

Analyze PR diffs against plans and docs to surface review items.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ingoatl/propertycentral --skill review-ingoatl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/ingoatl/propertycentral/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/ingoatl/propertycentral --skill review-ingoatl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes PR diffs and ensures alignment with the project plan and docs, surfacing actionable checks to prevent risky merges.

Core Features & Use Cases

  • Automated diff analysis: automatically scores risk and flags potential issues in a PR.
  • Scope drift detection: verifies changes remain faithful to the plan and TODOS.
  • Plan-ready output: generates concise notes to guide reviewers and feed plan workflows.

Quick Start

Initiate the /review workflow on the current branch to run a pre-landing PR review.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate pull-request reviews to detect scope drift before merging?

Automating pull-request reviews detects scope drift by analyzing PR diffs against project plans and docs. The review workflow scores risk, verifies plan consistency, and generates concise notes to guide reviewers before landing code changes.

Can I check if my PR diff aligns with the project plan and TODOs?

Checking PR diff alignment with project plans compares branch changes against documented TODOs. The scope drift detection mechanism flags potential issues and verifies changes remain faithful to the original plan, preventing risky merges.

Does automated pre-landing PR review work with both GitHub and GitLab workflows?

Automated pre-landing PR review works with both GitHub and GitLab workflows. It applies risk flags, scope drift checks, and plan-consistency verification across both platforms to surface actionable review items before merging.

What is the best way to surface actionable review items from a PR diff?

The best way to surface actionable review items from a PR diff is applying automated risk scoring and plan-consistency verification. This generates plan-ready output notes that feed plan workflows and guide human reviewers.

How do I run a pre-landing PR review on the current branch?

To run a pre-landing PR review on the current branch, initiate the /review workflow. This triggers automated diff analysis, scope drift detection, and risk flagging to surface actionable checks before merging.

When should I not use automated diff analysis for pull requests?

Automated diff analysis is not suitable for pull requests lacking an associated project plan or documentation. Without plan context to verify against, the scope drift detection and plan-consistency verification cannot effectively surface actionable review items.