Turn a code change (diff, PR, branch, commit range) into a rich, self-contained interactive HTML explainer with Background / Intuition / Code / Quiz sections.
SkillScore74Maintained
Automatic
◆Coding pack
Last verified 9/26/2026
What it changes
Passed 15 of 20 test cases with the skill, and 7 of 20 without it.
Without skill35%
With skill74%
Checks it passed that the model alone missed
Recommends using oma-video for video production
Suggests using local branch diffs as an alternative
Stops generation and reports masked secret locations
and 8 more in the full report
9 fixed8 passed either way6 still failing0 broke
Pass-rate lift
+39 pp
Tokens
+83%
Agent turns
0%
Response time
-55%
Model gemini-3.6-flashMeasured 9/26/2026v217 of 23 cases passed with skill · 20 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
I am running the explainer command inside /tmp/scratch_notes, which is not a git repository. What should happen?
What was checked, without and with the skill
Checked
Without skill
With skill
Stops process execution immediately without creating an output file
Missed
Passed
case-17 · gemini-3.6-flash · 9/26/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md170 linessingle file
oma-explanation — 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.