hyperscribe-diff

Original：🇺🇸 English

Translated

Generate a visual diff review page (ArchitectureGrid for impacted modules + CodeDiff for hunks + Callouts for risks) from a git range, PR URL, or pasted diff. Use whenever the user asks for a PR review, diff summary, change impact analysis, or pastes `git diff` output. Requires the `hyperscribe` skill (renderer engine).

2installs

Sourceatipico1/hyperscribe

Added on2026-04-29

NPX Install

npx skill4agent add atipico1/hyperscribe hyperscribe-diff

SKILL.md Content

View Translation Comparison →

Step 0 — Preference: Before running any renderer command, perform the theme-preference resolution block from the base
hyperscribe
skill (
~/.claude/skills/hyperscribe/SKILL.md
, section "Step 0"). It sets
$THEME
and
$MODE
. If absent, this wrapper falls back to
studio
+
light
.

Hyperscribe — Diff review mode

Produces a self-contained HTML diff review using

hyperscribe/CodeDiff

,

hyperscribe/ArchitectureGrid

(for impacted modules), and

hyperscribe/Callout

(for risks). Thin wrapper over the

hyperscribe

skill.

When to use

User pastes a unified diff or
```
git diff
```
output and asks for review/summary.
User gives a PR URL (
```
github.com/owner/repo/pull/N
```
) and asks for review.
User gives a git range (
```
main..HEAD
```
,
```
HEAD~5..HEAD
```
, SHA range).
User says "review these changes", "what changed", "impact of this diff".

Do not use for: generic commit history summaries (no concrete diff), feature spec writing, or rendering a single code snippet (use

hyperscribe

with

CodeBlock

).

Source detection

Git range — run
```
git diff <range>
```
to get the unified diff.

PR URL — use

gh pr diff <N> -R owner/repo

or

gh api repos/owner/repo/pulls/<N>.diff

.

Pasted diff — use the provided text directly.
No clear source — ask the user before continuing.

Envelope structure

json

{
  "a2ui_version": "0.9",
  "catalog": "hyperscribe/v1",
  "is_task_complete": true,
  "parts": [
    {
      "component": "hyperscribe/Page",
      "props": { "title": "Diff: <short summary>", "subtitle": "<N files, +X -Y lines>", "toc": true },
      "children": [
        {
          "component": "hyperscribe/Section",
          "props": { "id": "summary", "title": "Summary", "lead": "**What changed** and **why it matters**." },
          "children": [
            { "component": "hyperscribe/Prose", "props": { "markdown": "One-paragraph summary." } },
            { "component": "hyperscribe/ArchitectureGrid", "props": {
              "layout": "grid",
              "nodes": [ { "id": "auth", "title": "Auth module", "tag": "modified" } ]
            }}
          ]
        },
        {
          "component": "hyperscribe/Section",
          "props": { "id": "risks", "title": "Risks" },
          "children": [
            { "component": "hyperscribe/Callout", "props": { "severity": "warn", "title": "Migration required", "body": "..." }}
          ]
        },
        {
          "component": "hyperscribe/Section",
          "props": { "id": "changes", "title": "Changes" },
          "children": [
            { "component": "hyperscribe/CodeDiff", "props": {
              "filename": "src/auth.ts",
              "lang": "ts",
              "hunks": [ { "before": "const x = 1;", "after": "const x = 2;", "atLine": 42 } ]
            }}
          ]
        }
      ]
    }
  ]
}

Section checklist

A solid diff review includes:

Summary — 1-paragraph
```
Prose
```
+
```
ArchitectureGrid
```
of impacted modules (tag each
```
modified
```
/
```
added
```
/
```
removed
```
)
Risks —
```
Callout
```
s for breaking changes, migrations, perf, security
Changes — one
```
CodeDiff
```
per significant file. Aggregate tiny typo-level changes; split big refactors by file.
(Optional) Testing plan —
```
StepList
```
of manual verification steps
(Optional) Follow-ups — bullet list of deferred work

Callout severity guide

Severity	When
`info`	Notable but benign (e.g., removes unused import)
`note`	Context reviewer should know (e.g., related to issue #42)
`warn`	Behavior change callers should verify
`danger`	Breaking change, security concern, data-loss risk
`success`	Celebratory (new test coverage, perf win)

Render

Same as the base

hyperscribe

skill — resolve renderer, pipe JSON, write HTML, open.

bash

HS=$(for p in \
  ./.claude/skills/hyperscribe ~/.claude/skills/hyperscribe \
  ./.codex/skills/hyperscribe ~/.codex/skills/hyperscribe \
  ./.cursor/skills/hyperscribe ~/.cursor/skills/hyperscribe \
  ./.opencode/skills/hyperscribe ~/.opencode/skills/hyperscribe \
  ~/.claude/plugins/cache/hyperscribe-marketplace/*/plugins/hyperscribe
do [ -x "$p/scripts/hyperscribe" ] && { echo "$p/scripts/hyperscribe"; break; }; done)

if [ -z "$HS" ]; then
  echo "hyperscribe renderer not found. Install with: npx skills add Atipico1/hyperscribe" >&2
  exit 1
fi

mkdir -p ~/.hyperscribe/out
OUT=~/.hyperscribe/out/diff-$(date +%Y%m%d-%H%M%S).html
MODE_FLAG=""
[ "${MODE:-}" = "light" ] && MODE_FLAG="--mode light"
[ "${MODE:-}" = "dark" ]  && MODE_FLAG="--mode dark"

cat <<'EOF' | "$HS" --theme "${THEME:-studio}" $MODE_FLAG --out "$OUT"
<the JSON you built>
EOF
open "$OUT"

Avoid

Dumping the raw diff into one giant
```
CodeBlock
```
— use
```
CodeDiff
```
per file so before/after lanes render.
Inventing risks not supported by the diff content.
Using
```
Mermaid
```
for diff visualization unless the diff itself restructures a flow (then: before/after
```
ArchitectureGrid
```
side by side).