branch-reviewer

Review git branch changes for security, performance, and compatibility issues.

25|5|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/Nimbalyst/skills --skill branch-reviewer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-reviewer
Source: https://github.com/Nimbalyst/skills/tree/main/skills/dev/branch-reviewer
Command: npx skills add https://github.com/Nimbalyst/skills --skill branch-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a thorough, read-only code review of changes within a git branch, identifying potential issues before merging.

Core Features & Use Cases

  • Automated Code Audit: Analyzes code diffs for security, performance, compatibility, and bugs.
  • Structured Findings: Presents review results in a clear, categorized format.
  • Use Case: Before merging a new feature branch, use this Skill to get a detailed report on potential risks and areas for improvement.

Quick Start

Run a comprehensive review of the current branch changes.

Frequently Asked Questions about branch-reviewer

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

FAQPage Schema
How do I perform a comprehensive code review on my git branch changes?▼

To perform a comprehensive code review on your git branch changes, you can run an automated audit that analyzes code diffs for security vulnerabilities, performance bottlenecks, and potential bugs before merging.

Can I analyze both committed and uncommitted modifications during a branch analysis?▼

Yes, you can analyze both committed and uncommitted modifications during a branch analysis, as the review process performs a read-only scan of all current git branch changes to identify potential risks.

What specific issues does an automated code audit look for in a feature branch?▼

An automated code audit looks for security vulnerabilities, performance bottlenecks, cross-platform compatibility issues, type safety errors, potential bugs, and adherence to specific patterns like Jotai in a feature branch.

Does branch analysis work with Jotai pattern adherence and type safety checking?▼

Yes, branch analysis works with Jotai pattern adherence and type safety checking, evaluating your code diffs to ensure compliance with these specific structural requirements and generating a structured report with findings.

How do I get a structured report with suggested actions for security vulnerabilities in my code diffs?▼

To get a structured report with suggested actions for security vulnerabilities in your code diffs, execute a read-only branch review that categorizes findings and highlights areas for improvement before merging.

What are the limitations of using a read-only code review before merging a new feature branch?▼

A limitation of using a read-only code review before merging a new feature branch is that it only analyzes and reports on potential issues without directly modifying your code, requiring manual implementation of the suggested actions.