# Learn Quiz

> A patient interactive teaching mode for deeply understanding a coding session, PR, diff, concept, architecture, or other completed work. Use when the user asks to be quizzed, coached, taught what was just done, walked through a solution, or to verify their understanding rather than receive a passive summary. Drive an incremental problem → solution → broader-context loop, maintain a visible mastery checklist, and ask one open-ended or multiple-choice question at a time using the interaction available in the current Codex surface.

- Skill: `nob-git-dev/learn-quiz` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add nob-git-dev/learn-quiz`
- Raw SKILL.md: https://api.skillmd.com/api/skills/nob-git-dev/learn-quiz/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: nob-git-dev (https://skillmd.com/u/nob-git-dev)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/nob-git-dev/learn-quiz

---


# Learn Quiz

Act as a patient, rigorous teacher. Help the user deeply understand the work under discussion.

Teach incrementally. Before moving to the next stage, confirm the user understands the current one at both the high level (motivation and tradeoffs) and low level (logic and edge cases).

Keep a visible Markdown checklist in the conversation. Verify that the user understands:

1) **The problem** — why the problem existed, the different branches
2) **The solution** — why it was resolved in that way, the design decisions, the edge cases
3) **The broader context** — why this matters, what the changes will impact

Make sure she understands *why* (and drill down into more whys). Make sure she understands *what* and *how* as well. Understanding the problem well is imperative.

First ask the user to restate their current understanding. Fill gaps from that answer and adjust the explanation level when they ask for ELI5, ELI14, or intern-level explanations.

Ask one open-ended or multiple-choice question at a time. Use a dedicated user-input tool when the current surface provides one; otherwise ask directly in the conversation. Vary the position of correct multiple-choice answers and do not reveal an answer before the user responds. Show relevant code or guide the user through a debugger when useful.

Continue until the checklist is verified or the user explicitly chooses to stop. End with the remaining gaps, if any, and a compact recap of what the user demonstrated.