review-map

Generates a private HTML walkthrough mapping a pull request diff onto the system architecture.

49|11|Updated Jul 31, 2026
One-click install
npx skills add https://github.com/vstorm-co/agenticos --skill review-map-vstorm-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-map
Source: https://github.com/vstorm-co/agenticos/tree/main/.claude/skills/review-map
Command: npx skills add https://github.com/vstorm-co/agenticos --skill review-map-vstorm-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large or cross-cutting pull requests are hard to hold in your head during review. This Skill projects the diff onto the system architecture map so a reviewer can see which components and interactions changed before reading the code line by line. ## Core Features & Use Cases - Architecture projection: Highlights the changed components and edges on the existing mermaid diagrams from docs/architecture.md, dimming everything else. - Before/after flows and reading order: Shows side-by-side flow sketches for each changed interaction and groups changed files by layer with risky hunks flagged. - Private ephemeral artifact: Publishes a self-contained HTML page via the Artifact tool, or writes it to the scratchpad when the tool is unavailable. - Use Case: A reviewer faces a PR touching routes, services, repositories, and a migration. Run this Skill to get a visual map of what lights up, plus a suggested reading order with permission-gate and transaction-boundary changes flagged. ## Quick Start Ask the agent to run the review-map skill on PR 142 to produce a visual walkthrough of the changes.

Frequently Asked Questions about review-map

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

FAQPage Schema
How do I review a large pull request that touches many components?▼

Use this Skill to project the diff onto the architecture map from docs/architecture.md. It highlights changed components, draws before/after flows, and suggests a reading order grouped by layer with risky hunks flagged.

How to visualize a pull request diff on a system architecture diagram?▼

The Skill reads the mermaid diagrams in docs/architecture.md, identifies which boxes and edges the diff touches, and redraws the touched slice as inline SVG in a self-contained HTML page with everything else dimmed.

Does the review map work with stacked branches?▼

Yes. Without a PR number it diffs the current branch against its own base resolved via gh pr view, falling back to the repository default branch. This avoids folding the parent branch's changes into the walkthrough.

Can I use this without the Artifact tool or artifact-design skill?▼

Yes. Neither ships in the repository, so when they are absent the Skill writes the same walkthrough as a self-contained HTML file in the scratchpad directory with inline CSS and SVG, and hands over the file path instead of a URL.

When should I skip generating a review map?▼

Skip it for trivial or small single-layer diffs. The Skill is designed for genuinely large or cross-cutting changes, such as PRs touching routes, services, repositories, and frontend together, or a migration plus a spec change.