VS Code · Cursor · Windsurf · VSCodium
Green tests say it works. Not that you understand it.
After a commit or a green test run, Atomic Reps asks about the mechanism behind the change, in the panel beside your terminal. You answer from memory, with one key, and read why. Miss it, and it comes back later.
code --install-extension AtomicReps.atomicrepsAfter your commit fix(panel): stop the close animation hanging
A panel holds 4000px of content and closes with the rule below. What does the box you can see do during the 300ms?
.panel { max-height: 9999px; transition: max-height 300ms linear; }
.panel.is-closed { max-height: 0; }The question comes from the change you just made.
The extension reads which files changed, on your machine, and turns them into a few topic keys such as react or migrations. Those keys are what the server receives, and a question already written about that topic comes back.
It asks when a piece of work finishes, never while you type.
Saving happens in the middle of a thought, which is the worst moment to ask anybody anything. So the extension waits for the moments that mean a piece of work finished, and each one is a switch of its own.
How often a rep may come is a setting: a daily cap and a minimum gap, with off as one of the choices. Atomic Reps: How the moments land opens a table of what it noticed and what you did about it, so you can judge the rate before you change it.
Or ask for one. A keystroke gives you a short explanation of one mechanism, with no question attached.
The same rep, inside your coding agent- A commit
- made in the editor, in a terminal, or by an agent.
- A push
- when the branch reaches the remote.
- A green task
- a test or build task that finished without errors.
- A terminal command
- one on your list, such as pnpm test or cargo build, when it exits clean.
- Coming back
- after a break away from the editor, ten minutes by default.
- A debug session ending
- off by default; a session often ends mid-thought.
- You asking
- cmd+alt+r on a Mac, ctrl+alt+r elsewhere.
Your streak, your skills and your settings, in the panel.
The strip across the top of the panel has four screens. Rep is the question. Me is your summary, your skills with the accuracy behind each one, your last reps and a twelve week grid of the days you practised. Settings is the pace, the confidence tap and the areas a rep may come from, each saving as you change it. Doctor shows the server this machine talks to, when the next rep is due and the last error, and checks the server.
05 · One record, every door
One sign in. The question waiting in the editor is the one waiting everywhere else.
The extension shares its sign in and its open question with the command line tool, the MCP server and the Claude Code hook. Answer in whichever window you have open and the record moves once.
Install it in the editor you already use.
VS Code
From the Marketplace, or with one command in any terminal.
code --install-extension AtomicReps.atomicrepsCursor · Windsurf · VSCodium
The same package is published to Open VSX, which those editors read. Search for Atomic Reps in the extensions view, or install the .vsix by hand.
Open on Open VSXThen run Atomic Reps: Connect this editor. A browser tab opens with a short code already on your clipboard. Paste it and approve. That is the same sign in as npx atomicreps.
AtomicRepsInstall it in the editor you have open
The next time you commit, answer a question about what changed without leaving the file.
code --install-extension AtomicReps.atomicreps