review-branch

Generate a file-by-file code review from a git diff against a target branch.

2|Updated Jun 1, 2017
One-click install
npx skills add https://github.com/carlos-algms/dotfiles --skill review-branch-carlos-algms
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-branch
Source: https://github.com/carlos-algms/dotfiles/tree/main/AI-configs/skills/review-branch
Command: npx skills add https://github.com/carlos-algms/dotfiles --skill review-branch-carlos-algms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly review what changed in a branch by turning a git diff into a structured, file-by-file code review instead of doing manual comparisons.

Core Features & Use Cases

  • Branch diff orchestration: Reviews the current branch changes against a target branch (defaulting to origin/HEAD), or focuses on a user-provided subset of files.
  • Subagent delegation: Routes each file to a code-reviewer subagent when available, otherwise uses generic subagent mechanisms while preserving the code-reviewer constraints.
  • Consistent review artifacts: Uses repository-root files for shared context, a review todo list, and an aggregated markdown result, producing an organized output suitable for PR discussions.

Quick Start

Ask the AI to run the review-branch workflow for your current branch against origin/HEAD and write the aggregated results into review_result.md.

Frequently Asked Questions about review-branch

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

FAQPage Schema
How do I generate a code review from a git diff between branches?

To generate a code review from a git diff, this Skill compares your current branch against a target branch like origin/HEAD, filtering out binary and generated files, and aggregates a structured file-by-file markdown report.

Can I review only specific changed files instead of an entire branch diff?

Yes, you can review a user-provided subset of files instead of the entire branch diff. The workflow focuses on changed files only, excluding lock, generated, binary, and whitespace-only changes.

What is the best way to automate PR-style feedback for markdown reporting?

Automating PR-style feedback involves routing changed files to subagents for review and aggregating the outputs into a structured markdown report. This creates organized artifacts suitable for PR discussions without including raw git output.

Does this code review workflow filter out lock files and generated code?

Yes, the code review workflow filters out lock files, generated code, binary files, image files, and whitespace-only changes. This ensures the review focuses only on meaningful source code modifications.

Do I need subagents to run the branch comparison workflow?

Subagents are used for delegating per-file reviews but are not strictly required. If a code-reviewer subagent is unavailable, the workflow falls back to generic subagent mechanisms while preserving the same review constraints.

What files are created during the branch review process?

The branch review process creates repository-root files including review_context.md for shared context, review_files.md for the file list, and review_result.md for the final aggregated markdown report.