Code-review markdown → 2-column HTML
Converts a markdown code review or PR writeup containing diff fenced blocks and severity-tagged callouts into a single-file 2-column HTML review. The output features a unified diff on the left, severity-tagged annotation cards on the right, a top jump-nav listing every finding, and a mandatory named reviewer footer.
✨ What it does
- Parses markdown into diff hunks and extracts severity-tagged annotations.
- Renders a 2-column layout: unified diff on the left, annotation cards on the right.
- Generates a top jump-nav with severity badges and counts.
- Enforces WCAG 1.4.1 by using color plus icon and aria-label for severity badges.
- Requires a named reviewer via --reviewer and refuses without it.
- Produces a single-file HTML with inline CSS, responsive to viewport width.
🎯 When to use it
- When the markdown-html-orchestrator classifies an input as REVIEW.
- When the user directly invokes /cs:md-review with a markdown file.
- When the input contains ```diff fenced blocks and severity callouts like > [!BLOCKER] or > [!MAJOR].
- When you need a single-file HTML code review artifact with diff and annotations.
🚀 How to use
Trigger: /cs:md-review
Trigger by running /cs:md-review .md or by having the orchestrator route a REVIEW input. Provide a markdown file containing diff blocks and severity callouts. The skill expects a --reviewer argument (mandatory) and optionally a --title. Example prompts:
/cs:md-review review.md --reviewer "Jane Doe" --title "PR #123: Add retry logic"
Convert this code review markdown to HTML: [paste markdown]
📄 Output: A single-file HTML review at {default_output_dir}/review-{slug}.html.
📦 Add this skill to Claude Code
# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills
# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/markdown-html/skills/md-review .claude/skills/md-reviewSkill source: markdown-html/skills/md-review/SKILL.md
⚠️ Good to know
Requires a named reviewer (--reviewer) and at least one diff hunk; refuses inputs under 100 lines or without design-system onboarding.
❓ FAQ
What happens if I don't provide a reviewer?
The skill refuses to render and exits with code 3, because a code review must name a human reviewer.
Can I use custom severity names?
Yes, you can pass --severity-convention with a comma-separated list; the first item is the most severe.
What if there are no diff hunks in the markdown?
The skill refuses with exit code 4 and recommends routing to md-document instead.
🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.