PR walkthrough (reading guide for a human reviewer)
Help a human reviewer orient in a PR — not find bugs. Produce a markdown guide: where to start
(by centrality), what each file changes, and what it impacts ("careful, affects X"). Separate from
bug findings (review-pr).
Always answer the user in Russian (the project language). Tool calls, identifiers and path:line
stay verbatim.
Tools
Plus the PR-session tools (reviewer MCP): prepare_review, get_impact, get_changed_file_diff,
find_callers, get_related_symbols, read_file; optional get_subsystem_summaries (PRI-159);
optional post_pr_walkthrough (only on explicit user request).
Pipeline
Resolve repo & prepare the session. Resolve repo (git remote). Call prepare_review(repo, pr).
If it returns {"status": "skipped"} (branch not in REVIEW_BRANCHES), tell the user (in Russian)
and stop.
Reading order (centrality). Call get_impact(repo, pr) → changed symbols and their callers.
Order "start here" by how much depends on each changed symbol (most central first). Graph down →
fall back to ordering by file (fail-open).
What each file changes. For each changed file, get_changed_file_diff(repo, pr, path) → one
line describing what it changes.
Impact ("careful, affects X"). For the central changed symbols, find_callers /
get_related_symbols → who depends on them. Every "affects X" must be backed by a real caller.
Subsystem prior (optional). get_subsystem_summaries(repo, pr.base_ref, query="<PR title + changed file paths>") → name the touched
subsystem(s) in one line. Pass the PR's target branch pr.base_ref (from the prepare_review
response), NOT the local git branch — subsystem summaries are indexed per target branch
(base:<branch>). Empty / unavailable → skip (fail-open).
Assemble the guide (Russian markdown):
- Начни отсюда — ordered list (most central first).
- По файлам — one line per changed file.
- Осторожно, влияет на — impacted symbols + their callers.
- (optional) Подсистемы — 1–2 lines from summaries.
Output. Print the guide to the user by default. Post to the PR ONLY on explicit user request:
confirm first, then call post_pr_walkthrough(repo, pr, markdown) (posts a PR review comment with
a <!-- ai-walkthrough --> marker, separate from bug findings).
Grounding (hard rule)
Every "affects X" is backed by a real find_callers result. Never invent callers or impact.
Notes
- This is a reading guide, NOT a bug review — no findings, no inline severity comments.
- Posting to the PR is outward-facing and never happens without explicit user request + confirmation.
- Works without PRI-159 summaries and degrades gracefully when the graph is unavailable.
1---2name: pr-walkthrough3description: Build a human-facing reading guide for a GitHub pull request (where to start, what each file changes, what it impacts) using the reviewer PR session + code graph. Use when the user asks to walk a human reviewer through a PR ("PR walkthrough", "гид по PR", "как читать этот PR", "проведи по PR"). NOT a bug review (see review-pr). Requires the reviewer MCP server + base index.4---56# PR walkthrough (reading guide for a human reviewer)78Help a human reviewer orient in a PR — not find bugs. Produce a markdown guide: where to start9(by centrality), what each file changes, and what it impacts ("careful, affects X"). Separate from10bug findings (`review-pr`).1112**Always answer the user in Russian** (the project language). Tool calls, identifiers and `path:line`13stay verbatim.1415## Tools1617<!-- include: _common/tool-usage.md -->18Plus the PR-session tools (reviewer MCP): `prepare_review`, `get_impact`, `get_changed_file_diff`,19`find_callers`, `get_related_symbols`, `read_file`; optional `get_subsystem_summaries` (PRI-159);20optional `post_pr_walkthrough` (only on explicit user request).2122## Pipeline23241. **Resolve repo & prepare the session.** Resolve `repo` (git remote). Call `prepare_review(repo, pr)`.25 If it returns `{"status": "skipped"}` (branch not in REVIEW_BRANCHES), tell the user (in Russian)26 and stop.27282. **Reading order (centrality).** Call `get_impact(repo, pr)` → changed symbols and their callers.29 Order "start here" by how much depends on each changed symbol (most central first). Graph down →30 fall back to ordering by file (fail-open).31323. **What each file changes.** For each changed file, `get_changed_file_diff(repo, pr, path)` → one33 line describing what it changes.34354. **Impact ("careful, affects X").** For the central changed symbols, `find_callers` /36 `get_related_symbols` → who depends on them. Every "affects X" must be backed by a real caller.37385. **Subsystem prior (optional).** `get_subsystem_summaries(repo, pr.base_ref, query="<PR title + changed file paths>")` → name the touched39 subsystem(s) in one line. Pass the PR's target branch `pr.base_ref` (from the `prepare_review`40 response), NOT the local git branch — subsystem summaries are indexed per target branch41 (`base:<branch>`). Empty / unavailable → skip (fail-open).42436. **Assemble the guide (Russian markdown):**44 - **Начни отсюда** — ordered list (most central first).45 - **По файлам** — one line per changed file.46 - **Осторожно, влияет на** — impacted symbols + their callers.47 - (optional) **Подсистемы** — 1–2 lines from summaries.48497. **Output.** Print the guide to the user by default. Post to the PR ONLY on explicit user request:50 confirm first, then call `post_pr_walkthrough(repo, pr, markdown)` (posts a PR review comment with51 a `<!-- ai-walkthrough -->` marker, separate from bug findings).5253## Grounding (hard rule)5455<!-- include: _common/anti-hallucination.md -->5657Every "affects X" is backed by a real `find_callers` result. Never invent callers or impact.5859## Notes6061- This is a reading guide, NOT a bug review — no findings, no inline severity comments.62- Posting to the PR is outward-facing and never happens without explicit user request + confirmation.63- Works without PRI-159 summaries and degrades gracefully when the graph is unavailable.
hashgraph-online