quiz-me

Solid

Use right after writing or editing code or files for the user — before ending your turn — to quiz them on what was just built and confirm they actually understand it. Also triggers on "quiz me", "test my understanding", "check what I learned", "comprehension check", or recovering the understanding that vaporizes when you orchestrate an agent instead of authoring the code yourself.

AI & Automation 48 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
56
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /quiz-me — quiz the user on what was just built Adapted from the MIT-licensed no-numb plugin (github.com/Ciucky/no-numb); see `.claude/skills/ATTRIBUTION-no-numb.md`. Runs **host-side**. ## Overview After you write code for someone, they usually understand the result at a high level — what it does, its inputs and outputs — but not the internals or the *why*. That understanding "vaporizes." This skill has you administer a short comprehension quiz on **what you just did this turn**, so the understanding sticks. Being tested is itself the learning (retrieval practice); the quiz is not just a check. **Core principle:** quiz what *this turn* produced, from your own memory of what you just did — not generic trivia, not the whole codebase, not what the app does at a high level. ## When to run - Right after a turn in which you edited or wrote files, before finishing. - When the user runs `/quiz-me`. - When the no-numb Stop hook (`.claude/hooks/nonumb-gate.sh`) blocks your turn and asks you to quiz. (That gate is DEFAULT-OFF; it fires only when the user has opted in via `DEUS_NONUMB` or `~/.config/deus/nonumb.json`.) ## Step 1 — Is it worth quizzing? Look at what you changed this turn. **Bias toward quizzing.** Only skip when the change is *genuinely cosmetic*: formatting / whitespace, a variable rename, a CSS color tweak, a typo fix, a version bump. Everything else → quiz. **When in doubt, quiz.** If you do skip, say so in one line and stop — don't quiz on nothing. ## ...

Details

Author
sliamh11
Repository
sliamh11/Deus
Created
4 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

quizzing-the-session

Use when the user wants to be taught and quizzed on the work from the current session, what was just built, decided, debugged, or changed, to verify they deeply understand it. Also use right before opening a PR or merging, when the user wants to confirm they can represent the work in review. Not for updating agent instruction files; that is capturing-session-learnings.

0 Updated 1 weeks ago
pgoell
Code & Development Listed

quizzing-before-approving

Administers a structured comprehension quiz on a scoped code change to verify the reviewer genuinely understands it before approving or merging. Generates 5–7 questions in three batched rounds using a fixed rubric (restatement, alternatives, invariant, failure-mode, scope, targeted trickiest lines), grades strictly, provides context without revealing answers on failures, and loops until the user passes. Use when the user wants to be quizzed on a diff, wants to verify their understanding before merging or approving AI-generated code, wants a comprehension check before approving, or says things like "quiz me on this change", "test my understanding of this diff", "quiz before approve", or "quiz me before I merge."

0 Updated 6 days ago
msewell
Web & Frontend Listed

quizzing-a-topic

Use when the user wants to be taught and quizzed on a topic, theme, or concept they name (not the current session), to verify they deeply understand it. For example "teach me about Kafka consumer groups and test me" or "quiz me on this repo's auth flow".

0 Updated 1 weeks ago
pgoell