mcpField
M
make-pr-easy-to-review

make-pr-easy-to-review

github.com/ericlitmanDevelopment53223 installsUpdated 1w ago
Repository

About make-pr-easy-to-review

A skill for preparing pull requests so reviewers can understand their intent, key files, and risks. It favors review notes and safe improvements, and requires agreement before rewriting history.

Key features

  1. 01Inspect commits, diffs, and changed paths
  2. 02Flag reviewability issues
  3. 03Propose a plan before history changes
  4. 04Verify changes preserve intended code
  5. 05Add reviewer-focused PR guidance

Use cases

  1. 01Clarifying a PR with mixed or noisy changes
  2. 02Improving a PR description and reviewer entry points
  3. 03Planning history cleanup with approval

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/ericlitman/open-pstack --skill make-pr-easy-to-review

After installing, type/make-pr-easy-to-reviewin Claude Code to confirm it loaded.

Details

From the project README

Make PR Easy to Review

Prepare a PR so a reviewer can quickly understand the intent, important files, and risk. The default goal is reviewability without behavior changes.

Workflow

  1. Resolve the target PR from the user-provided URL or current branch.
  2. Inspect commits, diff size, changed paths, generated files, and PR description.
  3. Identify reviewability issues: noisy commits, stale description, unrelated changes, mixed mechanical and logic changes, missing tests, or unclear reviewer entry points.
  4. Propose a plan before rewriting history or force-pushing.
  5. Apply safe improvements, then verify the tree or diff still matches the intended code.

History Cleanup

Only rewrite history when the user asks for it or agrees to the plan. Before rewriting:

gh pr view <PR> --json title,headRefName,baseRefName,state,commits
git fetch origin <headRefName> <baseRefName>
ORIGINAL_TREE=$(git rev-parse origin/<headRefName>^{tree})

Good commit groupings usually follow dependency order:

  1. Schema/storage or generated API definitions.
  2. Core logic.
  3. Wiring and integration.
  4. UI or surface behavior.
  5. Tests.

After rewriting, verify content identity:

echo "Original tree: $ORIGINAL_TREE"
echo "Current tree:  $(git rev-parse HEAD^{tree})"
git diff origin/<headRefName> --stat

Do not push if the tree changed unintentionally.

Reviewer Guidance

When code behavior should stay untouched, prefer PR description and review notes:

  • Add a TL;DR that matches the actual diff.
  • Separate core files from generated or mechanical files.
  • Call out risky behavior changes, migration order, rollout plan, and test coverage.
  • Link issue trackers, dashboards, or design docs when they explain intent.

Guardrails

  • Never hide meaningful behavior changes inside "cleanup".
  • Do not bypass hooks unless the user explicitly asks.
  • If the PR is too large to make reviewable with notes, recommend splitting instead of polishing around the problem.

Comments

Markdown supported