pr-merge-champion

PR Merge Champion

Overview

A systematic playbook for preparing, reviewing, and documenting pull requests to ensure they are high-quality, free of common oversights, and optimized for instant maintainer approval and merging.

When to Use This Skill

• Use when preparing to open a new pull request on GitHub or any Git hosting platform.
• Use when self-auditing a feature or bug-fix branch for code cleanliness and consistency.
• Use when trying to minimize review cycles and speed up the integration of your changes.

How It Works

Step 1: Pre-Flight Clean Up & Rebase

Before presenting your code to reviewers, clean up any workspace noise and ensure your branch is up to date:

1. Rebase your feature branch on top of the latest target branch (e.g., main or master) to resolve conflicts early.
2. Clean up untracked, temp, or swap files from your repository.
3. Run local linters, formatters, and compilers to ensure no stylistic or syntax errors exist.

Step 2: Critical Self-Review

Review your own diff line-by-line as if you were the reviewer. Look out for:

1. Leftover debugging statements (e.g., console.log, print, breakpoints, or custom debug flags).
2. Unnecessary changes, white-space only diffs, or commented-out code blocks.
3. Incomplete TODO comments that should be resolved or turned into tracked issues.
4. Correctness of error handling and edge cases