vibe-learn

Learn as your AI coding assistant builds.

You can outsource your thinking, but you can't outsource your understanding.

vibe-learn watches Claude Code, GitHub Copilot CLI, Codex, OpenCode, Grok Build, or Cursor and helps you understand what was built, why, and how — without changing how you work. Offline, bash + jq, no API keys.

Try it (under a minute)

Claude Code (plugin):

/plugin marketplace add gkaria/vibe-learn
/plugin install vibe-learn@vibe-learn

Everyone else (or Claude Code without plugins):

curl -fsSL https://raw.githubusercontent.com/gkaria/vibe-learn/main/scripts/setup.sh | bash

Then work as usual. After the assistant writes or edits a file, type /learn.

Requires jq — brew install jq / apt-get install jq.

New here?

1. Install with the plugin or the curl line above.
2. Work normally — give the assistant a real task that writes or edits files. vibe-learn logs in the background.
3. Type /learn — a recap grounded in what just happened. Then /quiz if you want to check you understood it.

The 10-minute walkthrough covers digest, briefing, and audio.

Commands

Command	What it does
/learn [question]	Explain what just happened, or answer a specific question from the session log
/digest	Structured session report: what was built, decisions, patterns, things to study
/quiz [topic|review]	Recall questions, one at a time; review re-asks shaky or stale concepts
/explain [file|topic]	Guided code tour of a file or subsystem the session touched

Results land in a small local knowledge ledger. Concepts you answer shakily come back until they stick.

How your assistant maps it

Assistant	How you invoke it
Claude Code	/learn — plugin: /vibe-learn:learn
GitHub Copilot CLI	Use /learn inside a prompt (a skill reference, not a built-in slash command)
Codex	Use vibe-learn to learn what happened.
OpenCode	/learn
Grok Build	/learn or /vibe-learn
Cursor	/learn or /vibe-learn

Install details, caveats, and per-project setup: docs/assistants.md.

What it looks like

Continuing a JWT session. /learn is a plain-language recap; /digest, /quiz, and /explain go deeper. The session briefing is a local HTML page you can open any time.

📘 What just happened:

• Added JWT auth middleware (src/middleware/auth.ts) — every request to a
  protected route now passes a token check before reaching the handler
• Wired it into the user routes (src/routes/user.ts), so /profile and
  /settings require a valid token
• Installed jsonwebtoken to sign and verify tokens
• Pattern worth knowing: middleware ordering — auth runs before the route
  handlers, so handlers can safely assume req.user exists

/digest

## 📘 Session Digest

### What Was Built
JWT authentication for the user routes: a reusable auth middleware that
verifies tokens and attaches the decoded user to the request.

### Key Decisions
- Middleware over per-route checks — one enforcement point, no duplication
- jsonwebtoken over hand-rolling — battle-tested signing and expiry handling

### Patterns Used
- Express middleware chaining and ordering
- Fail-closed auth (reject first, then continue)