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.
Source: hashgraph-online/awesome-codex-plugins → plugins/mimfort/rag_for_git/plugin/skills/pr-walkthrough/SKILL.md
1---2name: reviewer-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."4category: engineering-core5source_repo: hashgraph-online/awesome-codex-plugins6source_path: "plugins/mimfort/rag_for_git/plugin/skills/pr-walkthrough/SKILL.md"7source_url: https://github.com/hashgraph-online/awesome-codex-plugins/blob/HEAD/plugins/mimfort/rag_for_git/plugin/skills/pr-walkthrough/SKILL.md8metadata:9 source: https://skillmd.com/skills/hashgraph-online/reviewer-pr-walkthrough10---111213# PR walkthrough (reading guide for a human reviewer)1415Help a human reviewer orient in a PR — not find bugs. Produce a markdown guide: where to start16(by centrality), what each file changes, and what it impacts ("careful, affects X"). Separate from17bug findings (`review-pr`).1819**Always answer the user in Russian** (the project language). Tool calls, identifiers and `path:line`20stay verbatim.2122## Tools2324<!-- include: _common/tool-usage.md -->25Plus the PR-session tools (reviewer MCP): `prepare_review`, `get_impact`, `get_changed_file_diff`,26`find_callers`, `get_related_symbols`, `read_file`; optional `get_subsystem_summaries` (PRI-159);27optional `post_pr_walkthrough` (only on explicit user request).2829## Pipeline30311. **Resolve repo & prepare the session.** Resolve `repo` (git remote). Call `prepare_review(repo, pr)`.32 If it returns `{"status": "skipped"}` (branch not in REVIEW_BRANCHES), tell the user (in Russian)33 and stop.34352. **Reading order (centrality).** Call `get_impact(repo, pr)` → changed symbols and their callers.36 Order "start here" by how much depends on each changed symbol (most central first). Graph down →37 fall back to ordering by file (fail-open).38393. **What each file changes.** For each changed file, `get_changed_file_diff(repo, pr, path)` → one40 line describing what it changes.41424. **Impact ("careful, affects X").** For the central changed symbols, `find_callers` /43 `get_related_symbols` → who depends on them. Every "affects X" must be backed by a real caller.44455. **Subsystem prior (optional).** `get_subsystem_summaries(repo, pr.base_ref, query="<PR title + changed file paths>")` → name the touched46 subsystem(s) in one line. Pass the PR's target branch `pr.base_ref` (from the `prepare_review`47 response), NOT the local git branch — subsystem summaries are indexed per target branch48 (`base:<branch>`). Empty / unavailable → skip (fail-open).49506. **Assemble the guide (Russian markdown):**51 - **Начни отсюда** — ordered list (most central first).52 - **По файлам** — one line per changed file.53 - **Осторожно, влияет на** — impacted symbols + their callers.54 - (optional) **Подсистемы** — 1–2 lines from summaries.55567. **Output.** Print the guide to the user by default. Post to the PR ONLY on explicit user request:57 confirm first, then call `post_pr_walkthrough(repo, pr, markdown)` (posts a PR review comment with58 a `<!-- ai-walkthrough -->` marker, separate from bug findings).5960## Grounding (hard rule)6162<!-- include: _common/anti-hallucination.md -->6364Every "affects X" is backed by a real `find_callers` result. Never invent callers or impact.6566## Notes6768- This is a reading guide, NOT a bug review — no findings, no inline severity comments.69- Posting to the PR is outward-facing and never happens without explicit user request + confirmation.70- Works without PRI-159 summaries and degrades gracefully when the graph is unavailable.7172---7374**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/mimfort/rag_for_git/plugin/skills/pr-walkthrough/SKILL.md`