mcpField
C
code-review-html

code-review-html

github.com/channTesting & quality039 installsUpdated 3w ago
Repository

About code-review-html

A variant of the code-review skill that produces Markdown reports and an interactive HTML report. The HTML supports Korean and English, with per-finding comments, Markdown copying, and feedback generation.

Key features

  1. 01Generate Markdown and interactive HTML reports
  2. 02Toggle between Korean and English
  3. 03Show severity badges and syntax highlighting
  4. 04Offer light, dark, and code color schemes
  5. 05Use a collapsible sidebar and per-finding comments
  6. 06Copy individual findings or feedback

Use cases

  1. 01Read code review results in bilingual HTML
  2. 02Comment on findings in a browser
  3. 03Copy findings or feedback for refinement

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/chann/skills --skill code-review-html

After installing, type/code-review-htmlin Claude Code to confirm it loaded.

Details

From the project README

Code Review (HTML Report)

Overview

Variant of the code-review skill that produces markdown reports and a self-contained, interactive HTML report.

The HTML report is bilingual (Korean + English with a full-page language toggle, Korean shown by default) and includes: severity badges, syntax highlighting with a light/dark/auto theme and an 8-option code scheme selector, a compact collapsible/resizable sidebar, per-finding "Copy Markdown", per-finding comments stored in the browser, and a "Copy feedback" button that emits a regeneration payload to refine the review.

Workflow

Before starting, Read the main code-review SKILL.md at <plugin-root>/skills/code-review/SKILL.md — the Review Process steps, severity table, language reference mapping, and report markdown template all live there. The variant relies on those sections.

The main skill's Evidence-first writing contract and conditional-section rules are authoritative. Do not restate or weaken them here.

Then follow the Review Process in the main SKILL.md exactly — steps 1–6 all apply, including HTML generation.

In short:

  1. Determine review scope and run the matching git diff (see "Determining Review Scope" in the main SKILL.md).

  2. Run diff_stats.py, load language-relevant references, and common-vulnerabilities.md if needed.

  3. Analyze the diff against the five dimensions and assign severities. Give every finding a stable [CR-001]-style ID.

  4. Write two markdown files with identical structure (same IDs, same code blocks):

    • .reviews/<YYYY-MM-DD>_<short-sha>.md — Korean, **Language:** ko (the main report).
    • .reviews/<YYYY-MM-DD>_<short-sha>.en.md — English, **Language:** en.

    Follow the main skill's Evidence-first writing contract and preserve its parser-significant English metadata keys.

  5. Run python <skill-path>/scripts/generate_html_report.py .reviews/<report>.md (it auto-detects the .en.md sibling and merges both into one HTML), then open it.

  6. For this persisted HTML mode, use a fact-only handoff containing finding counts by severity, overall risk, the Markdown and HTML artifact paths, fresh verification, and the browser-open fact or warning. Do not repeat report prose or promise a fixed finding count.

Include a .reviews/ ignore suggestion in this handoff only when artifacts were generated and .reviews/ is not ignored. Never modify .gitignore automatically.

The script lives at <plugin-root>/skills/code-review/scripts/generate_html_report.py (in the main skill — variants share it).

Filename

  • .reviews/<YYYY-MM-DD>_<short-sha>.md — Korean report (primary)
  • .reviews/<YYYY-MM-DD>_<short-sha>.en.md — English report (translation)
  • .reviews/<YYYY-MM-DD>_<short-sha>.html — merged bilingual HTML

See "Quick Reference / Filename convention" in the main SKILL.md.

Language

Bilingual by default — write both Korean and English (see "Bilingual HTML reports" in the main SKILL.md). Set **Language:** ko / en in each file's header so the generator labels and toggles them correctly, and keep finding IDs identical across the two files so per-finding comments stay attached when the reader switches language. If the user explicitly asks for a single language, write just that file; the generator falls back to a single-language report with the toggle hidden.

Red Flags

Same Never/Always lists as the main <plugin-root>/skills/code-review/SKILL.md. In particular: never modify .gitignore automatically (suggest only); never comment on code outside the diff.

Integration

Pairs with: git-commit — review before committing for a final quality gate.

Comments

Markdown supported