review

Reviews branch diffs against the base branch for structural issues before merging.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review before landing a PR often misses structural problems that tests do not catch, such as SQL safety issues, scope drift from the original plan, and incomplete implementations. This Skill automates a pre-landing review of your branch diff so problems surface before merge, not after. ## Core Features & Use Cases - Diff-Based Structural Review: Analyzes the current branch's diff against the detected base branch (GitHub, GitLab, or git-native fallback) for SQL safety, LLM trust boundary violations, and conditional side effects. - Scope Drift & Plan Completion Audit: Compares the diff against TODOS.md, PR descriptions, commit messages, and plan files to detect scope creep and missing requirements, classifying each plan item as DONE, PARTIAL, NOT DONE, or CHANGED. - Greptile Comment Triage: Fetches and classifies existing Greptile review comments as actionable, already fixed, false positive, or suppressed. - Use Case: Before merging a feature branch, run the review to get a scope check summary and a findings report covering structural issues, then decide whether to land or fix first. ## Quick Start Ask the assistant to review this PR or run a pre-landing review of my current branch diff.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a PR diff before merging?▼

Run the review workflow on your feature branch. It detects the base branch via gh, glab, or git-native fallbacks, fetches the diff, and checks for structural issues like SQL safety and scope drift before you land the change.

What is scope drift detection in code review?▼

Scope drift detection compares your branch's diff against the stated intent from TODOS.md, PR descriptions, commit messages, and plan files. It flags out-of-scope changes as scope creep and unaddressed requirements as missing, without blocking the review.

Does this code review work with GitLab merge requests?▼

Yes. The workflow detects the platform from the git remote URL and uses glab to find the merge request target branch. If CLI authentication fails, it falls back to git-native commands like symbolic-ref to determine the base branch.

Can the review check if my plan was fully implemented?▼

Yes. The plan completion audit extracts actionable items from a discovered plan file and classifies each as DONE, PARTIAL, NOT DONE, or CHANGED based on evidence in the diff, then reports a completion summary.

What happens if there is no diff against the base branch?▼

The review stops early with a message that there is nothing to review. It checks the current branch and runs a diff stat against the base branch before proceeding with any analysis steps.