pr-retro

Analyze feature branch health and merge readiness from git data.

5|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/namanchopra/branchwater --skill pr-retro-namanchopra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-retro
Source: https://github.com/namanchopra/branchwater/tree/main/.claude/skills/pr-retro
Command: npx skills add https://github.com/namanchopra/branchwater --skill pr-retro-namanchopra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, read, glob, grep, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you quickly analyze the health of a feature branch and determine its readiness for merging, providing detailed metrics and actionable recommendations.

Core Features & Use Cases

  • Branch Analysis: Compare all commits on the current branch vs the base branch, compute size metrics, test LOC ratio, focus score, session analysis, commit hygiene, contributor breakdown, and self-review scan.
  • Merge Readiness: Delivers a merge readiness verdict (GREEN/YELLOW/RED) based on various metrics and findings.
  • Use Case: Before creating a pull request, run this Skill to ensure the branch is in good shape and ready for merging.

Quick Start

Use the pr-retro skill to analyze the current branch's merge readiness.

Frequently Asked Questions about pr-retro

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

FAQPage Schema
How do I check feature branch merge readiness before creating a pull request?

Feature branch merge readiness is checked by analyzing git data to compute size metrics, commit hygiene, and focus score, delivering a GREEN, YELLOW, or RED verdict to ensure the branch is ready for merging.

What metrics are included in a feature branch health analysis?

Feature branch health analysis includes test LOC ratio, focus score, session analysis, commit hygiene, contributor breakdown, self-review scan, and size metrics comparing all commits against the base branch.

Do I need bash and git to analyze my feature branch for code review?

Yes, analyzing a feature branch for code review requires bash, read, glob, and grep dependencies to process git data and generate detailed metrics and actionable merge recommendations.

What's the best way to identify commit hygiene issues on a feature branch?

The best way to identify commit hygiene issues is to run an automated branch analysis that compares all commits against the base branch and flags problems alongside a self-review scan.

How does a merge readiness verdict work for feature branches?

A merge readiness verdict works by evaluating various git metrics and findings from the feature branch analysis, outputting a simple GREEN, YELLOW, or RED status to indicate if the branch is safe to merge.