Turn a code change (diff, PR, branch, commit range) into a rich, self-contained interactive HTML explainer with Background / Intuition / Code / Quiz sections.
SkillScore76Maintained
Automatic
◆Coding pack
Last verified 8/15/2026
What it changes
Passed 17 of 22 test cases with the skill, and 9 of 22 without it.
Without skill40%
With skill76%
Checks it passed that the model alone missed
User confirmation is required before proceeding with redacted text
The filename uses the YYYY-MM-DD date format based on Asia/Seoul timezone
The quiz defaults to exactly 5 questions unless an explicit count is requested
and 6 more in the full report
9 fixed10 passed either way6 still failing0 broke
Pass-rate lift
+36 pp
Tokens
+50%
Agent turns
0%
Response time
-67%
Model gemini-3.6-flashMeasured 8/15/2026v119 of 25 cases passed with skill · 22 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
My system prompt is written in French, but `.agents/oma-config.yaml` has `language: es`. Which language should be used for the prose and quiz in the generated document?
What was checked, without and with the skill
Checked
Without skill
With skill
The prose and quiz language prioritizes the prompt language over the configuration file setting
Missed
Passed
case-12 · gemini-3.6-flash · 8/15/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md160 linessingle file
oma-explainer — Interactive HTML Code-Change Explainer
Scheduling
Goal
Generate an educational, self-contained interactive HTML document that explains a code change to
a reader — deep skippable background for newcomers, core intuition with toy data, a comprehension-
ordered code walkthrough, and a five-question quiz — saved under .agents/results/explain/ and
validated against a deterministic checklist.
Intent signature
User invokes /explain, names this skill, or asks for a rich explanation/walkthrough of a
diff, PR, branch, or commit range (설명서, 해설, コード解説, 代码讲解).
Another skill or workflow delegates "explain this change 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
When NOT to use
Narrated explainer video → use oma-video (explainer mode); this skill produces HTML documents
Checking whether docs still match the codebase → use oma-docs (drift detection)
Finding defects or issuing review verdicts → use oma-qa (or the review workflow); this
skill narrates a change educationally, it does not evaluate it
Expected inputs
Target ref, resolved in this order:
Explicit argument — PR number (#640, via gh pr diff), branch (git diff main...{branch}),
or SHA range (a..b / a...b)
Staged changes (git diff --cached)
Dirty working tree (git diff)
Fallback HEAD~1..HEAD
Reader level: onboarding (default — full deep background) | reviewer (condensed background)
Output language: i18n-guide order — prompt language → .agents/oma-config.yamllanguage → en.
Prose and quiz in the user's language; code, identifiers, and inline code always English.
Quiz question count: default 5; changed only on explicit request.