pr-walkthrough-reporter

PR Walkthrough Reporter

Generate one slide-ready markdown PR walkthrough with plain markdown fallback from direct PR evidence. Write the artifact under WORK_ROOT, then output only single-line JSON containing the relative artifact path.

<evidence_json> {{EVIDENCE_JSON from prompt}} </evidence_json>

<kb_root> {{KB_ROOT from prompt}} </kb_root>

<work_root> {{WORK_ROOT from prompt}} </work_root>

<code_root> {{CODE_ROOT from prompt}} </code_root>

<review_id> {{REVIEW_ID from prompt}} </review_id>

1. Load Context

Read:

1. {KB_ROOT}/index.md
2. {KB_ROOT}/patterns.md

Load {KB_ROOT}/architecture.md only when the changed files in EVIDENCE_JSON.file_names span multiple architectural modules or top-level product areas. Use the KB module map when available; otherwise treat distinct top-level directories such as cli/, plugins/, docs/, evals/, and web-ui/ as separate areas.

If KB files are missing, continue with degraded context and rely on the evidence packet.

2. Parse Evidence

Parse EVIDENCE_JSON as the only source of truth.

Expected fields include:

• source: github_pr or git_diff
• target, base_branch, head_ref, review_id
• pr: PR metadata or git-only branch metadata
• file_names: changed file inventory
• patch: direct diff evidence or selected patch excerpts
• stats: diff stat or PR size metadata
• commit_summaries: commit subjects or PR commit objects
• evidence_index: objects with id, kind, source, and summary

Do not read .rp1/work/pr-reviews/ or any existing generated review artifact. Do not use prior reports as source material.

Evidence ID Rules

• Treat evidence_index as canonical.
• Every evidence ID cited in the walkthrough must appear in the Evidence Index table.
• Major purpose, change, reviewer-focus, and risk claims must cite one or more IDs inline.
• Prefer specific IDs: purpose claims use E-PR-###; file-scope claims use E-FILE-###; implementation/risk claims use E-DIFF-###; sequencing or intent claims use E-COMMIT-###.
• If a necessary direct source exists in EVIDENCE_JSON without an ID, create the smallest useful additional ID from that source and include it in the Evidence Index.
• Do not cite unsupported claims. If evidence is weak, phrase the point as a reviewer question.