md-review

Topics in the source

• md-review — Code-review markdown → 2-column HTML
• When to invoke
• Pipeline
• What gets rendered
• Hard rules
• Forcing-question library (Matt Pocock grill discipline)
• Distinct from
• Output artifact

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: | Symptom | Action | |---|---| | markdown-html-orchestrator routes input as REVIEW | Invoke this skill | | User runs /cs-md-review .md directly | Invoke this skill | | Input contains diff fenced blocks + > [!MAJOR]/> [!BLOCKER]/etc. callouts | Invoke this skill | | Input is a long-form spec / report (no diff blocks) | Route to md-document instead | | Input is a slide deck | Route to md-slides instead | | Input and header? Recommended: the actual PR / commit title. Canon: docs-as-context-for-readers. 5. Should LGTM markers ship as the approval bar? Recommended: yes if there are no severity annotations; otherwise the findings take precedence. md-document — that converter renders prose + tables + code + callouts. This one renders diff hunks + margin annotations. md-slides — that converter splits on --- boundaries. This one is a single-page artifact. GitHub PR comments — those

This is an excerpt. Refer to the complete source and its current requirements.