review

Cross-references Git branch diffs with developer checkpoint transcripts to identify mismatches between intended and actual code changes.

208|14|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/entireio/skills --skill review-entireio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/entireio/skills/tree/main/skills/review
Command: npx skills add https://github.com/entireio/skills --skill review-entireio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Standard code reviews only display code changes, missing the context of why those changes were made. This leads to missed mismatches between a developer's intended behavior and actual implementation, which can introduce bugs, security flaws, or unintended side effects before merging code.

Core Features & Use Cases

  • Intent Context Integration: Pulls checkpoint transcripts from the Entire CLI to understand the original goals, constraints, and edge cases discussed during development.
  • Comprehensive Diff Auditing: Checks for logic errors, security vulnerabilities, performance issues, error handling gaps, and leftover debug artifacts across all changed files.
  • Use Case: When merging a feature branch that refactors user authentication, this skill verifies the implementation matches the original intent discussed in the session, flags any unhandled edge cases, and catches leftover debug logging that should be removed before merge.

Quick Start

Ask your agent to review the current branch changes before merging to get an intent-aware audit of your code.

Frequently Asked Questions about review

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

FAQPage Schema
How do I perform an intent-aware code review before merging a Git branch?

Intent-aware code review cross-references branch diffs with developer session checkpoint transcripts to identify mismatches between intended and actual implementation before merging. This verifies your original goals and constraints are met by the code changes.

Can I audit uncommitted Git changes for security vulnerabilities and logic errors?

Yes, you can audit uncommitted changes alongside committed ones for security vulnerabilities and logic errors. The skill performs comprehensive diff auditing across all changed files to catch error handling gaps and leftover debug artifacts.

Do I need the Entire CLI to review branch changes, or does it work with just a diff?

You do not need the Entire CLI; the skill falls back to diff-only review when checkpoint data is unavailable. When the CLI is present, it pulls checkpoint transcripts to provide deeper intent context for the code audit.

What is the best way to verify my branch implementation matches the original development intent?

The best way is to cross-reference your Git diff with session checkpoint transcripts to detect mismatches between intended behavior and actual implementation. This catches bugs, security flaws, and unintended side effects that standard code reviews miss.

How are code review findings structured when auditing a feature branch?

Code review findings are output as a structured report grouped by severity and file path. This organization helps you quickly prioritize and locate logic errors, performance issues, and edge case gaps across the changed files.

What happens if checkpoint context is unavailable for a pre-merge check?

If checkpoint context is unavailable, the skill automatically falls back to a diff-only review. It still audits the Git changes for logic errors, security vulnerabilities, and performance issues without the intent context.