Individual 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.
plugins/mimfort/rag_for_git/plugin/skills/pr-walkthrough/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,532
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,435 bytes
Read excerpt
# 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);