review

Name: review
Availability: InStock
Author: him55710-sudo

Analyze code changes against the base branch to identify structural issues and risks.

Updated Mar 19, 2026

Search Tags:#review #code-quality #guardrails #pull-request #diff-analysis #plan-file

Ready to run

npx skills add https://github.com/him55710-sudo/uni-foli --skill review-him55710-sudo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/him55710-sudo/uni-foli/tree/main/.agents/skills/gstack-review
Command: npx skills add https://github.com/him55710-sudo/uni-foli --skill review-him55710-sudo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies structural issues, guardrails gaps, and potential risks in code changes to prevent bad merges and brittle releases.

Core Features & Use Cases

Diff analysis against the base branch to surface plan drift, missing tests, and edge-case gaps.
Actionable guidance for pre-landing PRs, code reviews, and audit workflows across multi-repo layouts.
Deterministic steps and guardrails to improve code quality and reduce risk before merging.

Quick Start

Run the review skill to analyze the current branch against the base branch and surface issues.

Frequently Asked Questions about review

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

FAQPage Schema

How do I review a pull request for structural issues before merging?▼

Pre-landing pull request review analyzes code changes against the base branch to identify structural issues, missing tests, and edge-case gaps. It enforces guardrails like planning checks and plan-file extraction to ensure maintainability and correctness before merging.

What is diff analysis and how does it catch code quality risks?▼

Diff analysis compares code changes against a base branch to surface plan drift, missing tests, and edge-case gaps. This mechanism identifies structural issues and potential risks not covered by tests, ensuring maintainability and reducing brittle releases.

Does the code review process work with multiple programming languages and project layouts?▼

Yes, pre-landing code review applies to diff-driven audits across multiple languages and project layouts. It enforces compatibility with repository conventions, ensuring traceable outcomes regardless of the specific multi-repo environment.

How do I extract a plan file to check for guardrail gaps during a code audit?▼

The review skill applies deterministic guardrails like planning checks and plan-file extraction during a code audit. This enforces repository conventions and identifies guardrails gaps to prevent bad merges and brittle releases.

When should I use an automated code review instead of manual inspection?▼

Use automated code review for pre-landing PRs and diff-driven audits to catch structural issues and potential risks fast. Manual inspection may miss plan drift, edge-case gaps, and missing tests across multi-repo layouts.