Convert Git diffs into interactive visual recap documents for review.
npx skills add https://github.com/Omniloy/agent-skills --skill visual-recap-omniloy
Please help me install this Agent Skill. Skill: visual-recap Source: https://github.com/Omniloy/agent-skills/tree/main/skills/visual-recap Command: npx skills add https://github.com/Omniloy/agent-skills --skill visual-recap-omniloy
This Skill helps reviewers understand substantial code changes without starting from a raw line-by-line diff. It turns a completed branch, pull request, or commit into a structured recap that surfaces what changed, why it changed, and where to look first.
Create a visual recap for the current pull request or branch diff and publish the interactive plan.
High-intent search queries and answers about installing and using this skill.
A visual recap organizes large multi-file pull request diffs into structured, interactive review artifacts. It uses diff-aware wireframes, file trees, and annotated split diffs to help reviewers understand substantial code changes without reading raw line-by-line diffs.
Reviewing large multi-file refactors is best handled by generating an interactive visual recap that structures changes into schema blocks and focused split diffs. This surfaces API contract shifts and architecture work clearly, preventing reviewers from getting lost in raw text.
Yes, you can generate visual recaps using a privacy-aware local-files workflow. This mode keeps your diff recaps entirely off the hosted Plan database, ensuring sensitive code changes and review artifacts remain strictly local to your environment.
A visual recap handles UI updates and API contract changes by applying diff-aware wireframes and structured schema blocks. This renders before-and-after states clearly, making it easier to inspect interface modifications and contract shifts during review.
You should avoid plain text summaries for pull request reviews when dealing with complex changes like architecture shifts, schema updates, or multi-file refactors. These substantial modifications require structured visual recaps with wireframes and file trees to provide proper review context.
RonnasaydGenerate structured Pull Request descriptions from git diffs and commit history.
hapticdataReview AI-generated plan files line-by-line in the LGTM terminal UI.
leonanpereirapintoGenerate self-contained HTML visual pages from Markdown content.
theneoaiSummarize git diffs into structured change summaries by file and change type.
