review

Analyze branch diffs for structural issues and classify plan items.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates a thorough pre-landing PR diff review, surfacing structural issues that tests may miss and guiding teams toward safer merges.

Core Features & Use Cases

  • Analyzes the current branch diff against the base branch for data-safety, LLM trust boundaries, and side-effect risks.
  • Extracts actionable work items from the plan and diff, classifies them into CODE, TEST, MIGRATION, and CONFIG categories, and reports DONE/PARTIAL/NOT DONE/CHANGED signals.
  • Provides actionable next steps and a plan-status summary to keep reviews aligned with project intent.

Quick Start

Run the /review workflow on your feature branch to surface potential merge blockers and a plan-driven completion audit.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate a pre-landing PR diff review for code quality?

Automated PR diff review analyzes the active branch against the base branch to surface structural issues like data-safety risks, LLM trust boundaries, and conditional side effects before merge.

How do I track plan-file scope drift in a pull request?

Tracking plan-file scope drift involves extracting actionable items from the plan and diff, classifying them into CODE, TEST, MIGRATION, and CONFIG, and reporting DONE, PARTIAL, NOT DONE, or CHANGED statuses.

What is the best way to audit feature completion against the project plan?

Auditing feature completion compares the active diff against the plan file to classify actionable items, providing a plan-status summary and actionable next steps for remediation anchored to project intent.

Can I review code for data-safety and side-effect risks before merging?

Pre-landing code review identifies data-safety, LLM trust boundary, and side-effect risks by analyzing structural issues in the current branch diff that standard tests may miss.

Does automated PR review work without external dependencies?

Automated PR review operates with zero external dependencies, directly analyzing the base branch diff and plan file to generate a completion audit and remediation steps.