report-walkthrough

Repackage delivery artifacts into reviewer-ready walkthroughs and PR bodies.

13|1|Updated Feb 7, 2026

Search Tags:#documentation #evidence #review #rfc #walkthrough #pr-body #report-walkthrough

Ready to run

npx skills add https://github.com/Thrimbda/legion-mind --skill report-walkthrough

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: report-walkthrough
Source: https://github.com/Thrimbda/legion-mind/tree/main/skills/report-walkthrough
Command: npx skills add https://github.com/Thrimbda/legion-mind --skill report-walkthrough

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Reorganizes existing delivery artifacts into reviewer-friendly summaries, enabling quick handoffs without creating new design or verification work.

Core Features & Use Cases

Re-packages implementation or RFC evidence into concise, reviewer-ready walkthroughs and PR bodies.
Supports two modes: implementation mode using entry evidence like docs/test-report.md and docs/review-change.md, or RFC-only mode using docs/rfc.md and docs/review-rfc.md. Exit evidence includes docs/report-walkthrough.md and docs/pr-body.md.
Guides auditability and traceability by standardizing how evidence is presented to reviewers.

Quick Start

Provide the current implementation handoff and required evidence to generate a reviewer-friendly walkthrough and PR body.

Frequently Asked Questions about report-walkthrough

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a reviewer-ready PR body from existing delivery artifacts?▼

Generate a reviewer-ready PR body by reorganizing existing delivery artifacts like test reports and review-change docs into concise walkthroughs. The Skill repackages implementation evidence into standardized summaries for quick handoffs without requiring new design or verification work.

What is the best way to summarize RFC evidence for a reviewer walkthrough?▼

Summarize RFC evidence for a reviewer walkthrough by using RFC-only mode, which processes docs/rfc.md and docs/review-rfc.md. This mode repackages the existing RFC materials into a reviewer-friendly format that satisfies auditability and traceability requirements.

How does report-walkthrough handle implementation handoffs differently from RFC reviews?▼

Report-walkthrough handles implementation handoffs by processing entry evidence like docs/test-report.md and docs/review-change.md, while RFC-only mode uses docs/rfc.md and docs/review-rfc.md. Both modes output reviewer-ready summaries and PR bodies tailored to their specific contexts.

Can I create reviewer-facing documentation without producing new design or verification work?▼

Yes, you can create reviewer-facing documentation without new design or verification work. The Skill repackages already-produced materials into concise walkthroughs, enabling quick handoffs by standardizing how existing evidence is presented to reviewers.

What input documents do I need to prepare before generating a reviewer-ready summary?▼

Prepare your current implementation handoff and required evidence files before generating a summary. For implementation mode, provide docs/test-report.md and docs/review-change.md. For RFC-only mode, supply docs/rfc.md and docs/review-rfc.md to produce the final walkthrough and PR body.

Why should I standardize how implementation evidence is presented to reviewers?▼

Standardize how implementation evidence is presented to reviewers to guide auditability and traceability. Reorganizing existing delivery artifacts into reviewer-friendly walkthroughs enables quick handoffs and clearly designates the mode as implementation or RFC-only for accurate context.