render-diff-html
/render-diff-html
Render git diffs and file-to-file comparisons as HTML or JSON reports with diff2html-cli. Use when the user asks to get, render, open, export, or show a visual diff; compare staged, unstaged, working tree, commit range, or last commit changes; convert a patch or .diff file; or show differences between two files or directories.
- Author
- alex-kopylov ↗
- Repository
- zweihander ↗
- Licence
- Apache-2.0
- Last repository change
- 19.10.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 19.10.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.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/render_diff_html.sh
What it does and when to use it
Render git diffs and file-to-file comparisons as HTML or JSON reports with diff2html-cli. Use when the user asks to get, render, open, export, or show a visual diff; compare staged, unstaged, working tree, commit range, or last commit changes; convert a patch or .diff file; or show differences between two files or directories.
Original author description
Render git diffs and file-to-file comparisons as HTML or JSON reports with diff2html-cli. Use when the user asks to get, render, open, export, or show a visual diff; compare staged, unstaged, working tree, commit range, or last commit changes; convert a patch or .diff file; or show differences between two files or directories.
How it works
- Quick Start
- Source Selection
- Options
- Verification
SKILL.md preview
---
name: render-diff-html
description: Render git diffs and file-to-file comparisons as HTML or JSON reports with diff2html-cli. Use when the user asks to get, render, open, export, or show a visual diff; compare staged, unstaged, working tree, commit range, or last commit changes; convert a patch or .diff file; or show differences between two files or directories.
---
# Render Diff HTML
Generate a visual diff report with `scripts/render_diff_html.sh`, which wraps
`diff2html-cli` and keeps raw diff generation consistent.
## Quick Start
Use the wrapper first. Pass git pathspecs after `--` when narrowing a git diff:
```bash
SCRIPT=plugins/dev-workflow/skills/render-diff-html/scripts/render_diff_html.sh
bash "$SCRIPT" --scope working
bash "$SCRIPT" --scope staged -- README.md
bash "$SCRIPT" --range origin/main...HEAD --style side
bash "$SCRIPT" --files old.txt new.txt
bash "$SCRIPT" --diff-file change.patch
```
Report the absolute output path to the user. If the user asks to preview it,
open that HTML path with the available browser or OS tool after generation.
## Source Selection
Prefer these simple mappings:
| User request | Wrapper option |
|---|---|
| "show my diff", "render the git diff" | `--scope working` |
| "staged changes" | `--scope staged` |
| "unstaged changes" | `--scope unstaged` |
| "last commit" | `--scope last` |
| "diff against main" | `--range origin/main...HEAD` |
| "compare A and B files" | `--files A B` |
| "convert this patch" | `--diff-file path/to/file.patch` |
Use `--output <path>` when the user gives a destination. Otherwise leave the
default `/tmp/codex-diff2html/...` output in place.
Internal diff files use `${ZWEIHANDER_TMP_DIR:-./.tmp/zweihander}/runs/render-diff-html/<run-id>/`.
The wrapper removes that run directory when it exits. This setting does not
change the report destination.
## Options
- Use `--style side` for side-by-side diffs and `--style line` for inline diffs.
- Use `--format html` by default; use `--format json` only when the user asks for machine-readable output.
- Use repeated `--ignore <path>` for noisy generated files such as lockfiles.
- Use `--title <text>` when a named report would help.
- Treat exit code `3` from the wrapper as "no differences found."
Read `references/diff2html-cli.md` only when you need raw `diff2html-cli`
details beyond the wrapper.
## Verification
After generation, verify that the output file exists and is non-empty. For HTML
reports, a basic check is enough:
```bash
test -s /absolute/path/to/report.html
```
Files in this package (4)
- SKILL.md 2 KB
- agents/openai.yaml 1 KB
- references/diff2html-cli.md 1 KB
- scripts/render_diff_html.sh 6 KB
Versions
The database has no other skills named render-diff-html.
Database snapshot: 13.11.2026 · package version 286d3035e064 (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
- 100pre-commit-review
Review local staged and unstaged tracked-file changes before committing or before a pull request exists. Use when the user invokes /pre-commit-review, asks for a pre-commit review, asks to review local changes before commit, or wants a local working-tree review before a PR exists. - 100review-diff
This skill should be used when a repoDir and an explicit diff scope (staged, unstaged, a commit, or a commit range) need reviewing with findings written back as inline diff comments — reviewing a colleague's branch, a pull request diff, or local uncommitted work, wherever the… - 86review-changes
Review current staged, unstaged, and untracked Git changes for correctness and regression risk, grounded in changed paths, diffs, focused file reads, and nearby test discovery. Use when the user asks to review local changes or a working-tree diff; do not use for broad repository audits. - 100ce-commit
Create a git commit with a clear, value-communicating message. Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate message. - 100commit-message-storyteller
Analyzes git diffs or staged changes and generates narrative commit messages that explain WHY a change was made, not just what changed — following Conventional Commits format. Use when asked to "write a commit message", "describe my changes", "what should I commit this as", or… - 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…