review

Analyzes pull request diffs against the base branch for structural issues and scope drift.

Updated May 1, 2026
One-click install
npx skills add https://github.com/ricardoo022/4dill --skill review-ricardoo022
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/ricardoo022/4dill/tree/main/.gemini/skills/review
Command: npx skills add https://github.com/ricardoo022/4dill --skill review-ricardoo022

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code review before merging often misses structural problems that tests do not catch, such as SQL safety issues, LLM trust boundary violations, conditional side effects, and scope drift where the branch does not match the stated plan. This Skill automates a pre-landing review of the current branch's diff against the base branch so these issues surface before code is merged. ## Core Features & Use Cases - Diff-Based Structural Review: Detects the git hosting platform (GitHub or GitLab), resolves the base branch, and analyzes the diff for SQL safety, trust boundary violations, and conditional side effects. - Scope Drift Detection: Compares the stated intent from TODOS.md, PR descriptions, and commit messages against the actual files changed to flag scope creep and missing requirements. - Plan Completion Audit: Discovers the relevant plan file, extracts actionable items, and classifies each as DONE, PARTIAL, NOT DONE, or CHANGED with evidence from the diff. - Use Case: Before merging a feature branch, ask for a review and receive a structured report covering plan completion, scope drift, and structural code issues with file and line references. ## Quick Start Ask the assistant to review this PR or check my diff before merging the current branch.

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 diff before merging?▼

Run the review workflow on your feature branch and it detects the base branch, fetches the diff, and analyzes it for structural issues like SQL safety and side effects. It also checks scope drift against your stated intent from commit messages and TODOS.md.

What does pre-landing code review check that tests miss?▼

It checks structural issues such as SQL safety, LLM trust boundary violations, and conditional side effects that unit tests typically do not cover. It also verifies the branch matches the planned scope by auditing plan file items against the actual diff.

Does this review workflow support GitLab merge requests?▼

Yes, it detects the platform from the git remote URL and uses glab CLI for GitLab or gh CLI for GitHub to resolve the target branch. If neither CLI is available, it falls back to git-native commands like symbolic-ref to find the default branch.

How does plan completion auditing work in code review?▼

The workflow locates the relevant plan file, extracts up to 50 actionable items such as checkboxes and numbered steps, then cross-references each against the diff. Items are classified as DONE, PARTIAL, NOT DONE, or CHANGED with cited file evidence.

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

If you are on the base branch or the diff is empty, the review stops immediately with a message stating there is nothing to review. This avoids running the full analysis pipeline on branches with no changes.