What problem does it solve?
Reviewing a code change without context is slow and error-prone: reviewers must reconstruct intent, find the important spots, and figure out how to verify behavior on their own. This Skill walks a human reviewer through a change step by step, from purpose and surface area to risk hotspots and hands-on verification.
Core Features & Use Cases
- Orientation and Intent Summary: Identifies the change from a PR, commit, branch, spec, or sprint status, then presents the intent and diff statistics (files changed, modules touched, boundary crossings, new public interfaces).
- Concern-Based Walkthrough: Organizes the review by design concerns rather than files, with clickable path:line stops ordered for comprehension, generating a review trail from the diff when none exists.
- Risk and Testing Guidance: Surfaces high-blast-radius spots tagged by category (auth, schema, billing, security, config) and suggests concrete manual observations to confirm the change works.
- Use Case: After a teammate opens a PR for an authentication refactor, invoke the walkthrough to get the intent summary, a guided tour of the key code locations, a list of risky spots like token validation changes, and commands to observe the new behavior before approving.
Quick Start
Ask the assistant to walk you through the current change or a specific PR, for example by saying "walk me through this change" or "walkthrough PR 42".
