visual-recap
SolidGenerate and maintain the system recap block in a PR description - a GitHub-rendered visual summary of which system primitives a change touches, how risky it is, and what changed. Prefer mermaid sequence diagrams for the change; pick another graph type when it explains the diff better. Use when planning a non-trivial change (plan mode), when creating or updating a pull request (recap mode), or when the user asks for a visual recap, visual plan, system review, or PR recap.
Install
Quality Score: 83/100
Skill Content
Details
- Author
- modem-dev
- Repository
- modem-dev/ossrules
- Created
- 1 weeks ago
- Last Updated
- 5 days ago
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
visual-recap
Turn a PR, branch, commit, or git diff into an interactive visual recap with diagrams, file maps, API/schema summaries, annotated diffs, and focused review notes.
visual-recap
Side-route skill that renders a change as a single self-contained interactive HTML artifact — a finished diff, PR, or branch, or a plan's decisions and architecture before any of it is built. Three block sets: a scrolling recap for auditing a change (file-tree + change flags, annotated split diffs with line-anchored callouts, schema/API contract cards, UI wireframes, before/after columns, a per-unit series when one root cause repeats across four or more near-identical sites), a paged walkthrough deck for arguing a reader through one (premise → changes → mechanism → aftermath), and forward-looking blocks for a plan (decision cards, options comparisons, architecture diagrams — every field cited or visibly asserted). Diagrams take a CSS spine when trivial and Mermaid-via-CDN when multi-stage or behavioral. Use when a reader who didn't author the change or the plan needs to grasp its shape before reading prose. Optional and never auto-invoked; skip small or obvious diffs, and plans whose decisions foreclose nothi
diff-recap
Turn a git diff into a PR-pasteable recap — one row per changed file whose path, status, and line counts are transcribed verbatim from `git diff --numstat` (true by construction; the model writes only the labels), emitted as an inline annotated widget plus a mandatory ASCII twin and a `diff-recap/1` record whose totals equal the sum of the rows. Fills the PR-summary gap the orient- family does not cover. Not /orient-map (shape + delta of the work) or /orient-status (position + ETA) — diff-recap recaps a concrete change-set. Zero external dependency: it renders inline, never to a hosted service.