skills.rest
RisorseArtificiali
RisorseArtificialiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pr-walkthrough

Reviews pull requests at the architecture level via Mermaid maps and interactive walkthroughs.

9|1|Updated Aug 28, 2026
Search Tags:#diff analysis#architecture#code review#pull request#mermaid#github#walkthrough
One-click install
npx skills add https://github.com/RisorseArtificiali/skills --skill pr-walkthrough-risorseartificiali
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-walkthrough
Source: https://github.com/RisorseArtificiali/skills/tree/main/skills/pr-walkthrough
Command: npx skills add https://github.com/RisorseArtificiali/skills --skill pr-walkthrough-risorseartificiali

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large or unfamiliar pull requests are hard to review by reading diffs alone; this Skill builds a visual map of what a PR logically changes and walks a human reviewer through it step by step, keeping the review above line-level code. ## Core Features & Use Cases - Seven-dimension logical review: evaluates intent, architecture, impacts and dependencies, user experience, operational impact, documentation drift, and test story with a traffic-light status per dimension. - Visual dossier: generates Mermaid before/after architecture diagrams and impact maps, persisted in .reviews/prs/ so the review survives session interruptions. - Interactive walkthrough: dispatches parallel scan and zoom subagents, then guides the reviewer through small sections with closed-menu questions, finding triage, and an optional GitHub comment draft approved verbatim before posting. - Use Case: A reviewer facing a 40-file PR asks for a walkthrough, receives a map of the 5 logical changes, triages each finding as real problem, accepted trade-off, or false alarm, and ends with author questions ready to post. ## Quick Start Walk me through PR 142 and build a visual review dossier of what it changes.

Frequently Asked Questions about pr-walkthrough

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

FAQPage Schema
How do I review a large pull request without reading every diff line?▼

Use a logical PR walkthrough that scans the diff with subagents, groups changes into 3-8 logical changes, and presents a Mermaid architecture map plus a traffic-light summary across seven dimensions. You then walk through only the red and yellow sections interactively.

What is the difference between PR walkthrough and code review?▼

PR walkthrough examines what a change does to the project's architecture, impacts, UX, operations, docs, and test story. Line-level correctness, style, and test quality belong to code review skills; code-level findings found during a walkthrough are parked for that separate pass.

Can I resume a PR review after my session ends?▼

Yes. The dossier is written to .reviews/prs/ and updated after every walkthrough section, so a new session can resume from it and re-scan only what new commits touched. The directory is excluded via .git/info/exclude, never .gitignore.

Does the walkthrough post comments to GitHub automatically?▼

No. It drafts a GitHub comment from the author questions and real problems at consolidation, shows you the exact text, and posts with gh pr comment only after you approve that verbatim wording.

When should I not use a logical PR walkthrough?▼

Skip it when you need line-level code review of correctness, style, or test quality, which belongs to review or adversarial-code-review skills. The walkthrough stays at reviewer altitude and parks code-level findings rather than debating them.

Related Skills

Explore More Software Engineering Skills→
guicauladaguicaulada
1

create-pr

Create GitHub pull requests with auto-generated titles and descriptions from branch commits.

Community
Advanced
ablyably
5

code-review-all

Coordinate parallel subagent reviews and synthesize severity-grouped findings into one verdict.

Official
Advanced
OpenCovenOpenCoven
20

serena

Navigate to and edit specific code symbols across multiple files.

Official
Intermediate
sapatamuku-creatorsapatamuku-creator

doubt-driven-development

Subjects non-trivial decisions to fresh-context adversarial review before they stand.

Community
Advanced