AGENT SKILL

pr-walkthrough

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.

License 许可
Apache-2.0
最近更新
2026-11-14
Stars
★ 1.6k
Forks
491

01 前言 Front Matter

name
pr-walkthrough
description
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.

03 SKILL.md 正文

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

<!-- include: _common/tool-usage.md --> 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

  1. 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.

  2. 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).

  3. What each file changes. For each changed file, get_changed_file_diff(repo, pr, path) → one line describing what it changes.

  4. 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.

  5. 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).

  6. 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.
  7. 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)

<!-- include: _common/anti-hallucination.md -->

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.

04 同仓库更多 Skills

hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-review-with-annotations

Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-find-and-synthesize-context

Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-create-or-update-docs

Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-create-or-manage-records

Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-create-or-manage-interactive-html

Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.

★ 1.6k
hashgraph-online
hashgraph-online/awesome-codex-plugins

worktable-collaborate-threads

Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.

★ 1.6k