review

Review feature branch commits against the original specification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when a feature branch is ready for review before merging. Use when the user says "review this", "look at these commits", or "check this branch". Also serves as the final verification gate — cross-references the original spec to catch completion bias. DO NOT use during implementation (per-commit reviews are built into /execute).

Core Features & Use Cases

  • Interactive, commit-by-commit analysis of a feature branch
  • Surface concerns, wait for reviewer signals, and rewrite history when needed
  • Serves as final verification by cross-referencing the original spec

Quick Start

Provide the target feature branch and any related issue or PR to initiate an interactive, commit-by-commit review.

Frequently Asked Questions about review

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

FAQPage Schema
How do I do an interactive code review for a feature branch?

Interactive code review evaluates a feature branch commit-by-commit against its original specification. It surfaces concerns, pauses for reviewer signals, and rewrites history when needed to catch edge cases before merging.

How does spec-verification work during a branch review?

Spec-verification cross-references the original specification against the feature branch commits. This serves as a final verification gate to catch completion bias and ensure the implemented history matches the requirements.

What's the best way to check commits for risk before merging a branch?

Per-commit risk assessment during branch review analyzes each commit individually. It requires access to Git history and issue or PR contexts to verify alignment and capture edge cases before history-preserving verification.

Can I use this code review during active implementation?

Code review is not used during implementation. Per-commit reviews are built into the execution phase, while this review serves as the final verification gate for a feature branch ready to merge.

Do I need access to Git history to review a feature branch?

Access to Git history is required to review a feature branch. The interactive analysis cross-references issue and PR contexts alongside commit history to verify alignment and rewrite history when needed.

What inputs do I need to start an interactive branch review?

Provide the target feature branch and any related issue or PR to initiate an interactive, commit-by-commit review. This context allows the analysis to cross-reference the original spec and capture edge cases.