Agent skill · creative production · alirezarezvani
md-review
Use when converting a markdown code review with diff blocks and severity callouts into a two-column HTML review. Parses diffs with diff_parser.py and annotations with annotation_extractor.py; requires a named reviewer.
Why this skill is useful
Adds 3 executable scripts for converting markdown code reviews into structured HTML outputs, which the AI cannot generate from knowledge alone.
What it needs
Requires python3 installed locally. About 3k tokens when loaded. Last updated 2026-08-05. 23,939 stars on the source repository.
What this skill does
md-review — Code-review markdown → 2-column HTML The code-review converter from Tier 2 of Shihipar's essay ("Code Review and PR Writeups"). Takes a markdown PR writeup with diff blocks + severity callouts and produces a single-file HTML review with a jump-nav, 2-column diff + annotation layout, and a named reviewer footer. Three stdlib tools pipeline together: When to invoke Symptom Action --- --- markdown-html-orchestrator routes input as REVIEW Invoke this skill User runs /cs-md-review <path>.md directly Invoke this skill Input contains bash 1. Parse markdown → diff hunks JSON python3 markdown-html/skills/md-review/scripts/diffparser.py \ --input <path>.md --output hunks.json 2. Extract severity-tagged annotations, attach to nearest preceding hunk python3 markdown-html/skills/md-review/scripts/annotationextractor.py \ --input <path>.md --diff-blocks hunks.json --output annotations.json 3. Render 2-col HTML (--reviewer is mandatory — refuses without) python3 markdown-html/skills/md-review/scripts/reviewhtmlrenderer.py \ --diff-blocks hunks.json --annotations annotations.json \ --reviewer "Jane Doe" --title "PR #123: Add retry logic" \ --output review.html What gets rendered Top jump-nav — every annotation with severity badge + 80-char preview + jump link; severity counts in the heading ("3 BLOCKER · 2 MAJOR · 1 NIT") 2-column hunk rows — unified diff on the left (per-line old/new line numbers, +/− marks, addition/deletion background tint from design-system tokens), annotation cards on the right (color + icon + aria-label per WCAG 1.4.1) Approval bar — if LGTM markers are present and no severity annotations, a success-tinted "LGTM — no findings flagged" bar General comments — annotations not attached to any hunk render at the bottom in their own section Reviewer footer — mandatory; refuses to render without --reviewer Responsive — 2-col collapses to stacked on viewports < 900px Hard rules 1. --reviewer is mandatory. A code review must name a human reviewer. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/md-review--a94933