How do I install the Diff Summary Md skill?

Run npx skillmds@latest add chann/diff-summary-md in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Diff Summary Md safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Diff Summary Md?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Diff Summary Md free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Diff Summary Md?

chann (@chann) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Diff Summary Md by chann — Agent Skill

Name: Diff Summary Md
Author: chann

Diff Summary Md

Use when the user wants a Markdown-only diff or change summary artifact without an HTML report, including "요약을 마크다운 파일로만 저장해줘", "마크다운 요약만 저장", "마크다운 요약만 만들어줘", "diff 요약 마크다운으로", "markdown-only diff summary", "summarize the changes into a markdown file", "summary file without HTML", "/diff-summary-md", or "$diff-summary-md". For the interactive HTML report use diff-summary; for a summary with a comprehension quiz use diff-summary-quiz; for defects use code-review.

chann ee9a354 7 files · 293.0 KB Updated Sep 17, 2026

File contents

Diff Summary (Markdown Only)

Overview

Variant of the diff-summary skill that persists aligned Korean and English Markdown reports to .diff-summaries/<date>_<scope-tag>.md and .diff-summaries/<date>_<scope-tag>.en.md. It never generates the HTML report and never attempts a browser open.

Workflow

Before starting, read the bundled base workflow at <skill-path>/references/diff-summary-workflow.md. It is a synchronized copy of the authoritative diff-summary workflow, including the packaged evidence collector contract, scope preservation and validation rules, untrusted-evidence rules, analysis dimensions, evidence-first writing contract, Explanatory Depth guidance, and Stable Report Contract. Do not restate or weaken it here.

Follow the bundled base workflow exactly through report authoring, then change only the generation step:

Collect the requested scope through the packaged evidence collector and its JSON standard-input contract, exactly as the bundled workflow requires. Every fail-closed rule applies unchanged.
Author the default aligned Korean and English Markdown pair that satisfies the bundled workflow's Stable Report Contract. Keep the same DS-* IDs, order, fields, and evidence claims in both languages.
Start the packaged generator with the same trusted absolute Python path and isolated -I mode, combining bilingual JSON input with --markdown-only:
```
/absolute/trusted/python3 -I <skill-path>/scripts/generate_summary_report.py \
  --bilingual-json-stdin \
  --output-directory ".diff-summaries" \
  --markdown-only
```
Send the exact {"ko":"<complete Korean Markdown>","en":"<complete English Markdown>"} object through standard input. The generator validates both full report contracts and their alignment, derives the collision-safe stem, and atomically writes only .diff-summaries/<date>_<scope-tag>.md and .diff-summaries/<date>_<scope-tag>.en.md. Require a zero exit status and use the exact absolute Markdown paths it prints.
Do not generate the HTML report. Do not attempt a browser open. Route requests for the interactive page to diff-summary or diff-summary-quiz instead of adding HTML output here.

Use the bundled workflow's single-language --markdown-stdin --markdown-only path only when the user explicitly requests one language.

This exact selector ships its own synchronized reference, collector, generator, and template so a standalone installation remains executable. Treat those bundled files as one release unit with the authoritative diff-summary runtime.

Conversation Handoff

Report only these artifact and verification facts: the exact requested scope and exact evidence command, the generated card count and both report languages, the two absolute Markdown output paths, fresh verification performed, and material unknowns that remain unverified. Do not repeat card or Executive Summary prose, and do not promise a fixed card count.

If .diff-summaries/ is not ignored by the target repository, suggest adding it to that repository's .gitignore. Never edit .gitignore automatically.

---name: diff-summary-mddescription: Use when the user wants a Markdown-only diff or change summary artifact without an HTML report, including "요약을 마크다운 파일로만 저장해줘", "마크다운 요약만 저장", "마크다운 요약만 만들어줘", "diff 요약 마크다운으로", "markdown-only diff summary", "summarize the changes into a markdown file", "summary file without HTML", "/diff-summary-md", or "$diff-summary-md". For the interactive HTML report use diff-summary; for a summary with a comprehension quiz use diff-summary-quiz; for defects use code-review.---# Diff Summary (Markdown Only)## OverviewVariant of the `diff-summary` skill that persists aligned Korean and English Markdown reports to `.diff-summaries/<date>_<scope-tag>.md` and `.diff-summaries/<date>_<scope-tag>.en.md`. It never generates the HTML report and never attempts a browser open.## Workflow**Before starting, read the bundled base workflow** at `<skill-path>/references/diff-summary-workflow.md`. It is a synchronized copy of the authoritative `diff-summary` workflow, including the packaged evidence collector contract, scope preservation and validation rules, untrusted-evidence rules, analysis dimensions, evidence-first writing contract, Explanatory Depth guidance, and Stable Report Contract. Do not restate or weaken it here.Follow the bundled base workflow exactly through report authoring, then change only the generation step:1. Collect the requested scope through the packaged evidence collector and its JSON standard-input contract, exactly as the bundled workflow requires. Every fail-closed rule applies unchanged.2. Author the default aligned Korean and English Markdown pair that satisfies the bundled workflow's Stable Report Contract. Keep the same `DS-*` IDs, order, fields, and evidence claims in both languages.3. Start the packaged generator with the same trusted absolute Python path and isolated `-I` mode, combining bilingual JSON input with `--markdown-only`: ```text /absolute/trusted/python3 -I <skill-path>/scripts/generate_summary_report.py \ --bilingual-json-stdin \ --output-directory ".diff-summaries" \ --markdown-only ``` Send the exact `{"ko":"<complete Korean Markdown>","en":"<complete English Markdown>"}` object through standard input. The generator validates both full report contracts and their alignment, derives the collision-safe stem, and atomically writes only `.diff-summaries/<date>_<scope-tag>.md` and `.diff-summaries/<date>_<scope-tag>.en.md`. Require a zero exit status and use the exact absolute Markdown paths it prints.4. Do not generate the HTML report. Do not attempt a browser open. Route requests for the interactive page to `diff-summary` or `diff-summary-quiz` instead of adding HTML output here.Use the bundled workflow's single-language `--markdown-stdin --markdown-only` path only when the user explicitly requests one language.This exact selector ships its own synchronized reference, collector, generator, and template so a standalone installation remains executable. Treat those bundled files as one release unit with the authoritative `diff-summary` runtime.## Conversation HandoffReport only these artifact and verification facts: the exact requested scope and exact evidence command, the generated card count and both report languages, the two absolute Markdown output paths, fresh verification performed, and material unknowns that remain unverified. Do not repeat card or Executive Summary prose, and do not promise a fixed card count.If `.diff-summaries/` is not ignored by the target repository, suggest adding it to that repository's `.gitignore`. Never edit `.gitignore` automatically.

Frequently asked questions