skills.rest
pontscho
pontschoCOMMUNITY
Explore all skills by this author →
GitHub

p:branch-review

Review a Git branch against its base branch for diffs, commits, and rule compliance.

1|Updated Jan 7, 2026
Search Tags:#git#merge#review#diff#code-quality#branch#pr
One-click install
npx skills add https://github.com/pontscho/prompt-heaven --skill p-branch-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: p:branch-review
Source: https://github.com/pontscho/prompt-heaven/tree/main/ClaudeCode/skills/p%3Abranch-review
Command: npx skills add https://github.com/pontscho/prompt-heaven --skill p-branch-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review current branch changes and ensure alignment with the base branch (master/main/trunk) before PR creation or merge, surfacing diffs, commit history, and rule-compliance insights to prevent regressions.

Core Features & Use Cases

  • Diff analysis: Compare changes against the base branch to surface statistics and exact file-level differences.
  • Commit overview: Summarize new commits and changes introduced on the feature branch.
  • Rule & quality checks: Apply project conventions and common config files to detect style or policy violations.
  • Use Case: Teams review a feature branch prior to merge to ensure compliance with coding standards and project rules.

Quick Start

Ask the AI to review the current branch against a base branch and report diffs, commits, and rule-compliance before PR creation.

Frequently Asked Questions about p:branch-review

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

FAQPage Schema
How do I review a git branch against master before creating a PR?▼

Review a git branch against master by analyzing diffs, summarizing new commits, and checking rule compliance to surface code quality issues before PR creation. This process highlights file-level differences and potential regressions.

Can I automatically check code quality and project rules on my feature branch?▼

Yes, you can check code quality on a feature branch by applying project conventions and common config files to detect style or policy violations. The review process categorizes these findings by severity for easier triage.

What is the best way to surface commit history and diffs before merging?▼

The best way to surface commit history and diffs before merging is to compare the current branch against a base branch. This summarizes new commits and extracts exact file-level differences to prevent regressions.

Do I need to specify a base branch for a git diff review?▼

You do not always need to specify a base branch for a git diff review. The review process can automatically detect common base branches like master, main, or trunk, though optional base branch input is supported.

Can I filter branch review findings by severity?▼

Yes, you can filter branch review findings by severity. The analysis applies rule and quality checks, categorizes the violations by severity, and produces a structured report with a final verdict.

What format are git branch review reports presented in?▼

Git branch review reports are presented in console, markdown, or both. The structured report includes diffs, commit overviews, severity-categorized findings, and a final verdict to guide merge decisions.

Related Skills

Explore More Software Engineering Skills→
sfc-gh-dflipposfc-gh-dflippo
34

skills-sync

Synchronizes AI agent skills from local SKILL.md files and remote Git repositories.

Community
Intermediate
thangvawnthangvawn

github-ops

Automate GitHub issue triage, pull request management, and CI/CD monitoring via gh CLI.

Community
Advanced
ianyimiianyimi
1

Global Coding Style

Enforce global coding style guidelines across multi-language codebases.

Community
Basic
AesopScottAesopScott

conflict-predict

Precompute merge conflicts and tune Git fetch and diff-risk parameters.

Community
Advanced