# Oma Explanation

Create an offline HTML explanation of a code change (diff, PR, branch) or of a topic...

- Repository: https://github.com/first-fluke/oh-my-agent (1356 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add first-fluke/oh-my-agent --skill oma-explanation -g -a claude-code -y`
Codex: `npx skills add first-fluke/oh-my-agent --skill oma-explanation -g -a codex -y`
Cursor: `npx skills add first-fluke/oh-my-agent --skill oma-explanation -g -a cursor -y`
Gemini CLI: `npx skills add first-fluke/oh-my-agent --skill oma-explanation -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add first-fluke/oh-my-agent`

## Description

Create an offline HTML explanation of a code change (diff, PR, branch) or of a topic, system, or question. Use when a visual walkthrough document is requested.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# oma-explanation, Interactive HTML Explainer

## Scheduling

### Goal
Generate an educational, self-contained interactive HTML document, saved under
`.agents/results/explain/` and validated against a deterministic checklist. Two modes:

- **Change mode**, explains a code change: deep skippable background for newcomers, core
  intuition with toy data, a comprehension-ordered code walkthrough, and a five-question quiz.
- **Topic mode**, explains a concept, a system, or the answer to a question as a one-page
  visual sheet: lead answer, then panels of diagrams, tables, and short prose.

In both modes the model writes a Markdown **draft** and `oma explain render` produces the HTML.
Layout, theme, diagram geometry, and the quiz script are the renderer's, not the model's.

### Intent signature
- User invokes `/explain`, names this skill, or asks for a rich explanation/walkthrough of a
  diff, PR, branch, or commit range (설명서, 해설, コード解説, 代码讲解).
- User asks for a visual / HTML explanation of a topic that is not a diff: how a system works,
  a comparison, an answer worth keeping as a page (`/explain how does the row planner work`).
- Another skill or workflow delegates "explain this as a document" output.
- Activation is slash/explicit/delegated only, this skill is intentionally excluded from
  keyword auto-detection ("explain" is everyday vocabulary; `convert` precedent).

### When to use
- Explaining a PR, branch, commit range, or the current staged/unstaged change as a document
- Onboarding a teammate onto a change they did not write
- Producing a reviewable teaching artifact after a large or subtle change lands
- Turning an architecture, a protocol, a comparison, or a long answer into one visual page

The rest: https://github.com/first-fluke/oh-my-agent/blob/HEAD/.agents/skills/oma-explanation/SKILL.md