branch-diff-code-review

Analyze branch code changes for bugs, regressions, and compliance issues.

16|3|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/Yomiamy/flutter_inspector_kit --skill branch-diff-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: branch-diff-code-review
Source: https://github.com/Yomiamy/flutter_inspector_kit/tree/main/.claude/skills/branch-diff-code-review
Command: npx skills add https://github.com/Yomiamy/flutter_inspector_kit --skill branch-diff-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of reviewing code changes in a branch, ensuring that all aspects of the code are thoroughly examined and documented in a structured and professional manner.

Core Features & Use Cases

  • Branch Diff Analysis: Inspects all code changes from the branch fork point to the current commit.
  • Bug and Regression Detection: Prioritizes identifying bugs and regressions in the code.
  • Compliance with Style Guide: Adheres to the repository's style guide and provides feedback in zh-tw.
  • Use Case: When a developer wants to review a branch that has diverged from its base branch and ensure that all changes are compliant with the repository's standards.

Quick Start

Run the 'branch-diff-code-review' skill to review all changes in the 'feature/new-branch' branch.

Frequently Asked Questions about branch-diff-code-review

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

FAQPage Schema
How do I review all code changes in a git branch against its base branch?

Branch diff analysis inspects all code changes from the branch fork point to the current commit to identify bugs, regressions, and style guide compliance issues. It operates using git diff and git log commands to capture the complete divergence history.

Can I detect regressions and bugs automatically using git diff history?

Yes, bug and regression detection prioritizes identifying regressions in the code by analyzing git diff and git log outputs. It examines branch changes to catch potential issues and ensure the new code does not break existing functionality.

Does branch code review work without specifying a target or base branch?

Branch code review requires a base reference to calculate the fork point and generate the git diff. Without a base branch or fork point, the review process cannot determine the scope of changes to analyze for bugs and style guide compliance.

What is the best way to ensure my branch updates comply with the repository style guide?

The best way to ensure style guide compliance is to run a branch diff analysis that checks all code changes against the repository's style guide. This process highlights any deviations and provides structured feedback in zh-tw.

How do I generate a code review report for a feature branch?

To generate a code review report for a feature branch, run the review skill on the target branch to analyze its git diff. It compiles the identified bugs, regressions, and style guide issues into a structured professional document.

Why is my code review report generated in zh-tw?

The code review report is generated in zh-tw because the review process is designed to adhere to the repository's style guide and provide feedback in zh-tw. This ensures the review output meets the specific language requirements of the repository.