skills.rest
westn
westnCOMMUNITY
Explore all skills by this author →
𝕏@westnGitHub

review

Identify structural issues in diffs and PR context before merging.

1|Updated Mar 15, 2026
Search Tags:#audit#quality#review#diff#plan#PR#pre-landing
One-click install
npx skills add https://github.com/westn/gstack-pi-port --skill review-westn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/westn/gstack-pi-port/tree/main/port/gstack/review
Command: npx skills add https://github.com/westn/gstack-pi-port --skill review-westn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes diffs and PR context to surface drift between requested work and the actual changes, catching missing tests, scope creep, and unsafe patterns before merging.

Core Features & Use Cases

  • Scope drift detection by comparing diffs, TODOS.md, PR bodies, and commit messages to ensure the work matches the plan.
  • Actionable plan auditing that extracts concrete tasks from plan files and cross-references them with the diff.
  • Pre-landing guidance including risk indicators, recommended next steps, and evidence collection for reviewers.

Quick Start

Run the /skill:review command on your current branch to start the 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 detect scope drift in a PR before merging?▼

To detect scope drift in a PR before merging, you analyze diffs and PR context to surface discrepancies between requested work and actual changes. This process cross-references diffs, TODOS.md, PR bodies, and commit messages to catch scope creep and missing tests.

What is pre-landing code review for catching unsafe changes?▼

Pre-landing code review identifies structural issues in diffs and PR context before merging. It surfaces drift, test gaps, and unsafe changes by reading the current branch, diffing against the base, and analyzing PR metadata to produce a structured assessment.

How do I audit a diff against my plan files and commit messages?▼

You audit a diff against plan files by extracting concrete tasks from plan files and cross-referencing them with repository changes. This actionable plan auditing compares diffs, TODOS.md, PR bodies, and commit messages to verify alignment with the requested work.

Can I get risk indicators and recommended next steps for PR reviewers?▼

Yes, you can generate risk indicators and recommended next steps for PR reviewers. The pre-landing review process provides actionable guidance by collecting evidence from the diff and PR metadata, highlighting unsafe changes and structural issues for reviewers.

Does pre-landing PR review work without external dependencies?▼

Yes, pre-landing PR review works without external dependencies. The review process requires no additional components, reading the current branch and diffing against the base directly to produce a structured assessment of test gaps and unsafe changes.

What is the best way to find missing test gaps in a branch diff?▼

The best way to find missing test gaps in a branch diff is to analyze the PR context against the base branch. This pre-landing review surfaces test gaps and structural issues by comparing the actual changes against the requested work in plan files.

Related Skills

Explore More Software Engineering Skills→
twikustwikus
3

create-pr

Create GitHub pull requests from the current branch using gh CLI.

Community
Intermediate
Andreicr1Andreicr1

schema-drift-detector

Cross-reference schema.rb changes against included migrations to detect drift in pull requests.

Community
Intermediate
mrkingsleyobimrkingsleyobi

github-code-review

Coordinate multi-agent code reviews for GitHub pull requests.

Community
Advanced
coreindustriescoreindustries
1

test

Execute automated tests with coverage reporting and quality gate enforcement.

Community
Advanced