review

Review branch diffs against base commits and report verified defects.

4|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Ni-Bu/skills --skill review-ni-bu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Ni-Bu/skills/tree/main/review
Command: npx skills add https://github.com/Ni-Bu/skills --skill review-ni-bu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you perform a deep, senior-engineer-level review of code changes so you can catch logic bugs, design mistakes, missing error handling, and convention violations before they reach production.

Core Features & Use Cases

  • Branch Review: Inspects the current branch against its PR base and summarizes verified findings by severity.
  • Context-Aware Analysis: Reads changed files in the context of surrounding code to understand how the patch fits into the broader system.
  • High-Signal Feedback: Focuses on real, actionable issues such as naming problems, inconsistent patterns, unsafe control flow, and missing edge-case handling.
  • Use Case: Use it when you want a thorough review of a feature branch, bug fix, refactor, or migration and need feedback that goes beyond linting.

Quick Start

Ask the review skill to review the current branch against its PR base and report only verified issues with clear severity and fix suggestions.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a git branch diff for logic bugs before a pull request?

Code review catches real logic bugs, design mistakes, missing error handling, and convention violations before they reach production, whereas linting primarily enforces stylistic formatting and syntax rules. Code review reads changed files in context to validate findings against the actual repository state.

Can I use automated code review on a refactoring branch?

Yes, you can use code review on refactoring branches. It inspects the branch diff against its PR base to identify verified defects in naming, control flow, and edge-case handling, providing high-signal feedback specifically tailored for refactoring changes.

What is the best way to detect missing error handling in a feature branch?

The best way to detect missing error handling in a feature branch is to perform a context-aware code review that reads changed files alongside surrounding code. This validates how the patch fits into the broader system and identifies missing edge-case handling.

How do I verify defect findings against the actual repository state?

To verify defect findings against the actual repository state, review the branch diff by reading the changed files in their full context rather than in isolation. This ensures reported issues like unsafe control flow are actual defects before reporting them by severity.

Does branch code review work for migrations and bug fixes?

Yes, branch code review works for migrations and bug fixes by inspecting the branch diff against its PR base. It provides thorough feedback on logic, design, naming, and error handling to catch verified issues before merge.