branch-review

Review local code diffs against the default branch and write a markdown report.

1|Updated Jan 2, 2020
One-click install
npx skills add https://github.com/otahontas/nix --skill branch-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: branch-review
Source: https://github.com/otahontas/nix/tree/main/home/configs/pi-coding-agent/skills/branch-review
Command: npx skills add https://github.com/otahontas/nix --skill branch-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically performs a local multi-angle code review against the default branch and writes a markdown report.

Core Features & Use Cases

  • Policy / AGENTS compliance: check diff against AGENTS.md guidance
  • Bug scan: inspect diff only (avoid large context)
  • History / blame: use git blame + git log on modified files/lines
  • Optional GitHub PR context: when on GitHub and gh is available, detect and compare with recent merged PRs touching modified files
  • Reporting: generate a concise markdown report highlighting issues, file changes, and suggested fixes

Quick Start

Run the branch-review skill from the repository root to generate the code-review.md report.

Frequently Asked Questions about branch-review

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

FAQPage Schema
How do I automate local code reviews against the default branch?

Automate a local code review by running the skill from your repository root to compute diffs against the default branch, evaluate changes, and generate a markdown report. It uses git diff and git blame to highlight issues and suggested fixes.

What is an AGENTS.md compliance check in a git diff?

An AGENTS.md compliance check evaluates your git diff against guidance defined in an AGENTS.md file. The skill scans changes to ensure code modifications align with established project policies and outputs the results.

How do I generate a markdown report for a git diff review?

Generate a markdown report for a git diff by running the skill in your local repository. It computes the diff, inspects for bugs, checks historical context via git blame, and writes the final report to a configurable path.

Does the code review skill require GitHub or gh to function?

The code review skill does not require GitHub or gh, relying only on Git and a local repository. The gh CLI is optional and used solely to fetch additional GitHub PR context when available.

Can I use git blame to add historical context to code review reports?

Yes, you can use git blame to add historical context to code review reports. The skill automatically runs git blame and git log on modified files and lines to provide historical background in the final markdown output.

What are the limitations of reviewing only the git diff without large context?

Reviewing only the git diff without large context limits detection of bugs requiring broader file knowledge, but ensures fast local execution. The skill focuses on the diff to inspect changes efficiently before generating the report.