visual-diff-review
/visual-diff-review
Use when asked to review a diff and produce a 7-section visual page. Not for interactive review walks or PR-specific review: use show-review.
- Author
- gosuda ↗
- Repository
- dalcom-skills ↗
- Licence
- Apache-2.0
- Last repository change
- 10.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use when asked to review a diff and produce a 7-section visual page. Not for interactive review walks or PR-specific review: use show-review.
Original author description
Use when asked to review a diff and produce a 7-section visual page. Not for interactive review walks or PR-specific review: use show-review.
How it works
- Building the seven sections, in order
- When evidence runs out
SKILL.md preview
--- name: visual-diff-review description: 'Use when asked to review a diff and produce a 7-section visual page. Not for interactive review walks or PR-specific review: use show-review.' --- # Drawing the change on one page You take a branch, commit, range, PR, or working tree, compare it against its base (`main` or `master` unless the user names another), and render the review as a single self-contained page at `diagrams/visual-diff-review.html` that you then open. The page carries seven sections in order -- Overview, Before State, After State, Risk Assessment, Coupling Analysis, Merge Recommendation, Evidence Log -- and every section cites its evidence or admits it has none. You touch nothing remote; the only mutation is that local page, and you state the rollback (delete or re-render the page) before writing it. ## Building the seven sections, in order 1. Resolve the named target to its base and extract the full diff. If the name does not resolve, report the exact name that failed and stop rather than widening scope; if the diff is empty, say no changes were found and stop. 2. Enumerate every affected file and component and classify the change surface. This is the scope everything later cites. 3. For each hunk, describe behavior before and after in concrete terms -- what the code did, what it does now. 4. Assess correctness, performance, security, and compatibility, each with evidence from the diff. 5. Name the cross-component dependencies and side-effect surfaces inside the diff. 6. Recommend merge, defer, or reject, grounded in the specific evidence from the earlier sections. 7. Write the page to `diagrams/visual-diff-review.html` and open it, or report the path if opening is unavailable. A filesystem error on write ends the run: report the error, roll back any partial file, and do not proceed to open. ## When evidence runs out A section you cannot support is marked `INSUFFICIENT EVIDENCE` and the review continues -- citations are never fabricated. A partially complete page is acceptable only when each incomplete section is labeled that way; silence is not a partial result.
Files in this package (2)
- SKILL.md 2 KB
- agents/openai.yaml 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · gosuda/dalcom-skills | 100 | Apache-2.0 |
| OutlineDriven/outline-driven-development | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 224f2302ddb3 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 87review
Use when you review this PR's diff. (gstack) - 90review
Review a pull request or diff for this repository against otari's project standards. Use when asked to review a PR, inspect a diff, or prepare review feedback. - 100visual-review
Two visual modes — render a PR diff as an HTML page with each hunk annotated by principle, or check a UI change in a real browser (screenshots, console, network). Use for a visual/HTML diff report, "check the UI", or "screenshot before/after". Don't use for text-only feedback… - 100revdiff
Pi-only interactive diff and file review with revdiff. Use when the user explicitly asks for revdiff, interactive annotations, or captured revdiff comments inside pi. - 90review-code
Code review flow — review a diff, PR, or code change, delegating the review to a subagent that follows the code-review-criteria skill. Use it when the user asks to review code or a PR, in any phrasing. - 90walk-the-diff
Use when the user wants to walk through their local changes interactively before or instead of a PR review — e.g., "guided review", "walk me through the changes", "review my branch", "let's go through the diff". Also use when the user explicitly invokes the walk-the-diff skill…