pr-org

Analyze commits between the current branch and main to propose a cleaner PR organization.

13|Updated May 19, 2024
One-click install
npx skills add https://github.com/david-crespo/dotfiles --skill pr-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-org
Source: https://github.com/david-crespo/dotfiles/tree/main/claude/skills/pr-org
Command: npx skills add https://github.com/david-crespo/dotfiles --skill pr-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR review often suffers from noisy commit histories that obscure intent and slow reviewers. This skill analyzes commits between the current branch and main and proposes a cleaner organization to improve clarity and review efficiency.

Core Features & Use Cases

  • Identify canceling commits and logical threads to surface meaningful changes.
  • Recommend grouping related commits into cohesive units and suggest a minimal, review-friendly PR structure.
  • Highlight coupling and divergent changes to guide consolidation decisions and reduce churn.

Quick Start

Review the commit history from main to the current branch and propose a clean, minimal PR organization with rationale.

Frequently Asked Questions about pr-org

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

FAQPage Schema
How do I organize commits in a feature branch for a cleaner PR review?

To organize commits for a cleaner PR review, analyze the history between your current branch and main to identify canceling commits, logical threads, and iterative changes, then propose a consolidation strategy that groups related commits into cohesive units.

What is the best way to consolidate multiple refactoring commits before a PR?

The best way to consolidate refactoring commits is to analyze the branch history to detect coupling and divergent changes, then group related iterative changes together to reduce churn and highlight meaningful changes for clearer review.

How does analyzing canceling commits improve my git branch history?

Analyzing canceling commits improves git branch history by identifying redundant changes that obscure intent, allowing you to surface only meaningful changes and recommend a minimal, review-friendly PR structure with clear rationale.

When should I reorganize my feature branch commits?

You should reorganize feature branch commits when your history contains multiple iterative changes, refactors, or reorganizations that require consolidation, and the noisy commit history begins to obscure intent and slow down reviewers.

Can I identify logical threads in a noisy git commit history?

Yes, you can identify logical threads in a noisy git commit history by analyzing the commits between your current branch and main to determine coupling and recommend grouping related commits into cohesive, review-friendly units.