pr-walkthrough

Walk through changed files and sections of a GitHub PR interactively.

Updated Nov 9, 2025
One-click install
npx skills add https://github.com/YoniChechik/claude-code-config --skill pr-walkthrough
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-walkthrough
Source: https://github.com/YoniChechik/claude-code-config/tree/main/skills/pr-walkthrough
Command: npx skills add https://github.com/YoniChechik/claude-code-config --skill pr-walkthrough

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Walks through a PR's changes interactively, explaining one file and one section at a time - like a human would sit and explain their code. Each step requires user to say "next" to continue.

Core Features & Use Cases

  • Interactive PR walkthrough mapping: walks through changed files and sections to present a review structure.
  • Step-by-step navigation: each step requires user input ("next") to proceed to the next section.
  • Flexible PR selection: accepts a specified PR number or uses the PR associated with the current branch.

Quick Start

Start an interactive PR walkthrough by invoking the pr-walkthrough skill with a PR number or by providing no argument to review the PR associated with the current branch.

Frequently Asked Questions about pr-walkthrough

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

FAQPage Schema
How do I do an interactive pull request walkthrough of changed files?

Use the pr-walkthrough skill to get an interactive pull request walkthrough that maps changed files and sections. You navigate by typing "next" to proceed through each code section during the review.

Can I review a GitHub PR diff step by step without specifying a PR number?

Yes, you can review a GitHub PR diff step by step without a PR number. The walkthrough automatically fetches and uses the pull request associated with your current working Git branch.

Do I need gh and jq installed to walk through PR changes?

Yes, you need both the gh CLI and jq installed to walk through PR changes. The skill relies on the gh pr view and gh pr diff commands to fetch PR data, and jq to parse the structured pull request information.

What's the best way to review code changes section by section instead of viewing the whole diff?

The best way to review code changes section by section is using an interactive walkthrough that splits the PR diff into logical steps. This method presents one file and one section at a time, requiring user input to continue.

How does a step-by-step PR review work for large pull requests?

A step-by-step PR review for large pull requests works by breaking down the diff into manageable file and section mappings. This interactive approach prevents reviewers from being overwhelmed by presenting changes incrementally.