GitHub - timini/drill-me · GitHub
/" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
/;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
timini
drill-me
Public
Notifications<br>You must be signed in to change notification settings
Fork
Star
main
BranchesTags
Go to file
CodeOpen more actions menu
Folders and files<br>NameNameLast commit message<br>Last commit date<br>Latest commit
History<br>5 Commits<br>5 Commits
.claude-plugin
.claude-plugin
docs
docs
skills
skills
.gitignore
.gitignore
LICENSE
LICENSE
README.md
README.md
View all files
Repository files navigation
🧠 drill-me
/grill-me taught Claude what you know. /drill-me teaches you what Claude knows.
A Claude Code plugin that turns Claude into an adaptive tutor with a long-term memory<br>of you. It quizzes before it explains, spaces reviews on a forgetting curve, keeps<br>you at the difficulty sweet spot, and remembers exactly what you were shaky on —<br>across sessions, across projects, forever (or until you rm -rf ~/.drill-me).
/drill:me rust lifetimes<br>/drill:me this repo's auth flow<br>/drill:me ~/papers/attention-is-all-you-need.pdf
(Yes, the command reads as a sentence. Or skip the slash entirely and just tell<br>Claude "drill me on rust lifetimes" — it knows what you mean.)
No walls of text. No "Great question! Here are 7 key points." One question at a time,<br>relentlessly — just in the other direction.
Why
/grill-me went viral because it inverted the<br>usual flow: instead of the model guessing what's in your head, it interrogates you<br>until your knowledge is in its head. One question at a time, no mercy.
drill-me is the mirror image. The model's knowledge → your head. And it turns out<br>cognitive science knows exactly how to do that transfer, and it's the opposite of how<br>chatbots normally behave:
Chatbots default to<br>The evidence says
Explaining things at you<br>Testing you — retrieval practice beats re-reading, g ≈ 0.61 (Roediger & Karpicke 2006)
Everything in one session<br>Spacing reviews on your forgetting curve (FSRS — the algorithm behind Anki)
Making it feel easy<br>~15% error rate is the optimal difficulty (Wilson et al. 2019, Nature Comms)
Walls of text<br>≤150 words per chunk , working memory holds ~4 items (Sweller, cognitive load theory)
Telling you the answer<br>Making you guess first — pretesting boosts retention even when you guess wrong
"You're absolutely right!"<br>Confidence ratings before the reveal — confident-wrong errors are the most correctable of all (the hypercorrection effect)
Every rule in drill-me's playbook has a citation. The full receipts are in<br>docs/the-science.md .
What a session looks like
You: /drill:me git rebase
Claude: Before we start — what do you already know about rebase?<br>Even fragments are fine.
You: it's like merge but rewrites history? i always just merge<br>because rebase scares me
Claude: That's a real starting point — and "scares me" is fixable.<br>Quick guess before I explain anything: when you rebase a<br>branch onto main, what do you think actually happens to<br>your commits?
You: they get... moved onto main?
Claude: Close — they get *replayed*. Git takes each of your commits,<br>turns it into a patch, and re-applies it on top of main.<br>New commits, new hashes. The old ones are abandoned, not moved.
So — your teammate has branch `foo` checked out, and you<br>rebase `foo` and force-push. Why is your teammate now sad?
You: because their local foo points at commits that don't exist<br>anymore?
Claude: ▸ How confident are you in that answer?<br>○ 1–2 Guessing<br>● 3 Fairly sure<br>○ 4–5 Certain
Claude: It's exactly right — and worth more confidence than a 3. ...
Next session opens with: "Last time we covered rebase — before anything new: without<br>looking, what's the difference between what merge and rebase do to history?" — because<br>that card is due today, and the card you flubbed is due first.
What it can teach
Anything Claude knows — /drill:me bayesian statistics, /drill:me kubernetes networking
Your own codebase — /drill:me this repo's payment flow. It explores the code<br>first, then drills you on it, anchoring every question to real file:lines. Great for<br>onboarding (or for finally understanding the legacy service you inherited).
Documents — point it at a PDF, a file, or...