review

Compare a branch diff against the base branch to detect scope drift and missing changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps reviewers quickly identify structural issues in a feature branch that tests may miss by comparing the branch diff to the base.

Core Features & Use Cases

  • Pre-landing PR review: validates the diff against the intended plan, detects scope drift, and surfaces missing work.
  • Plan-file alignment: cross-checks commit messages, PR body, and commit intent with the actual changes.
  • Actionable guidance: provides plan-completion-style feedback and suggested next steps to keep scope in check.

Quick Start

Run the review workflow on a feature branch to surface structural issues in the diff against the base branch.

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 pull request before merging?

Detect scope drift in a pull request by comparing the branch diff against the base branch and plan files. This validates commit intent against planned work to flag out-of-scope changes that tests miss.

What is the best way to review a git diff for structural issues?

Reviewing a git diff for structural issues involves comparing the feature branch against the base to identify missing changes, scope inconsistencies, and plan misalignment that automated tests typically will not catch.

Can I validate planned work against feature branch commits automatically?

You can validate planned work against feature branch commits by cross-checking commit messages and PR bodies with actual code changes. This enforces robust checks for scope alignment and plan completion.

Do I need plan files to perform a pre-landing PR review?

Plan files are required to perform a pre-landing PR review using this method. Access to git, the base branch, and plan documentation is necessary to validate scope and surface missing work.

What structural problems in a code diff will tests miss?

Structural problems in a code diff that tests miss include scope drift, incomplete feature implementation, and inconsistencies between commit messages and actual changes. Pre-landing reviews validate diff coverage against the plan.

When should I not rely on automated tests for branch review?

You should not rely solely on automated tests for branch review when checking for scope drift or missing planned changes. Comparing the diff against the base branch validates structural intent that tests cannot verify.