review

Generates structured pitfall reports for code diffs and change lists.

1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/tho/skills --skill review-tho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/tho/skills/tree/main/skills/review
Command: npx skills add https://github.com/tho/skills --skill review-tho

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you review code changes effectively so you can catch correctness, security, and design risks before a merge.

Core Features & Use Cases

  • Scope-aware reviewing: Review the user-requested scope (diffs, staged/unstaged changes, or branch diffs) and ask a clarifying question when scope is ambiguous.
  • Evidence-first judgment: Understand the stated intent (commit message, PR description, issues) before evaluating whether the implementation matches it.
  • Lens-driven findings: Load relevant review lenses by default, read each lens reference, and report only concrete issues with clear impact and suggested fixes.

Quick Start

Use the review skill to review a PR diff and generate a structured report with lens-grouped findings focused on real risks.

Frequently Asked Questions about review

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

FAQPage Schema
How do I perform a structured code review on a pull request diff?

To perform a structured code review, select the diff scope, collect commit intent and repository context, load relevant review lenses, and generate a report with concrete findings on correctness, security, and design risks.

What is the best way to assess merge readiness for staged or unstaged changes?

Assess merge readiness by evaluating staged or unstaged changes against stated intent, applying review lenses to identify correctness and safety risks, and producing a structured report to determine if the code is safe to merge.

How does lens-driven code review help identify PR risks?

Lens-driven code review applies specific perspectives like security and architecture to a diff, reporting only concrete issues with clear impact and suggested fixes to accurately assess PR risks before merging.

Can I review branch diffs and commit changes for correctness and safety?

Yes, you can review branch diffs and commit changes by applying review lenses to check correctness, safety, and design risks, ensuring the implementation matches the stated intent and meets merge quality standards.

What should I do when the review scope for a code diff is ambiguous?

When the code diff review scope is ambiguous, ask a clarifying question to determine whether to review staged changes, unstaged changes, or the full PR diff before loading review lenses and generating findings.

Does evidence-first judgment require a PR description to review code?

Evidence-first judgment uses available context like commit messages, PR descriptions, or issues to understand stated intent before evaluating whether the implementation matches it, ensuring accurate merge readiness assessment.