SkillFoxx

vibe-learn plugin

A plugin that watches your assistant: /learn explains what was built and why, and /quiz checks that you understood it.

  • 57 ★ on the repository
  • Last commit
  • MIT
Plugin

Extended access

Why this level

  • Session hooks write a log of assistant actions into the project and the setup script changes the agent configuration.
All reasons and checks

gkaria/vibe-learnAuthor:gkaria

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add plugins/vibe-learn

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Session hooks write a log of assistant actions into the project and the setup script changes the agent configuration.

This is third-party code. Review the repository files before installing.

What it does

vibe-learn watches Claude Code, GitHub Copilot CLI, Codex, OpenCode, Grok Build or Cursor without changing how you work. After the assistant writes or edits a file, `/learn` explains what resulted, why and how. `/digest` summarises the session, `/explain` unpacks a chosen fragment and `/quiz` asks questions, corrects a half-right answer and records the result in a knowledge ledger. It works offline with no keys, on `bash` and `jq`. Session hooks write a `.vibe-learn/session-log.jsonl` log in the project. Without that log, `/learn`, `/digest` and `/explain` fall back to `git status`, `git diff` and `git log`.

Who it is for. Developers who hand code to an assistant but want to understand what changed and keep their own skills sharp.

Good fit when

  • After a large assistant edit you want to understand how it works before accepting it.
  • At the end of a session you want a short recap of what was built and why.
  • You want a comprehension check: `/quiz` asks questions about recently written code.
  • The same skill set is needed across several assistants.

Not a fit when

  • You want finished code, not an explanation: the plugin writes nothing.
  • You do not want a session log kept in the project.
  • `jq` is missing and cannot be installed.

Example request

/learn

Limitations

It needs `jq`, installed with `brew install jq` or `apt-get install jq`. Setup differs per assistant: a plugin in Claude Code, a script for the others and a separate local plugin for Cursor. The setup script runs through `curl` and `bash`, so read it first. If you installed both the script and the Cursor plugin, keep only one or events log twice. Cursor admins may need to allow local plugins. Consider adding the `.vibe-learn` log to git-ignored files.

How to disable. Remove the plugin with Claude Code or delete `~/.cursor/plugins/local/vibe-learn` for Cursor. Delete the `.vibe-learn` folder in the project by hand.

FAQ

How do I install it in Claude Code?

Run `/plugin marketplace add gkaria/vibe-learn`, then `/plugin install vibe-learn@vibe-learn`.

How do I install it for other assistants?

Run the repository's `scripts/setup.sh`, installed with the `curl` and `bash` command in the README. Cursor also has a separate local plugin.

Do I need keys or a network?

No. The plugin works offline on `bash` and `jq` and asks for no keys.

What does /quiz do?

It asks about recent code, corrects a half-right answer and records the result in a knowledge ledger. It needs a session log or the ledger.

What if the session log is empty?

`/learn`, `/digest` and `/explain` use `git status`, `git diff` and `git log`.

Discussion

No questions or reviews yet.

Plugins

VibeWise turns coding with an agent into learning: it asks for your approach first, you make the design decisions, and the agent writes the code

SkillExtended access4.3K

A plugin makes the agent explain its code and, before a push, ask questions so you understand what you are merging.

PluginExtended access65

VibeGit is a local version safety net that saves checkpoints before agent edits and rolls a project back after a failure.

PluginExtended access297

Over 150 skills for building apps on the ibl.ai platform: sign-in, agent chat, profiles, analytics, desktop and mobile builds

PluginBroad access229

A skill that explains and audits code, telling you what it does and why instead of just accepting it

SkillExtended access1.1K

A Claude Code plugin and CLI that keep agent code matching the patterns of the repository and offer MCP checking tools.

PluginExtended access60

README in short

The plugin ships for Claude Code, Cursor and other assistants through adapters, with `learn`, `digest`, `quiz`, `explain` and shared `vibe-learn` skills plus session hooks. The README includes a demo of `/quiz` correcting a half-right answer.

README badge

Original SKILL.md

---
name: vibe-learn
description: Explain, digest, quiz, and tour the code of the current vibe-learn coding session, with cross-session knowledge tracking and optional Obsidian save and recall workflows grounded in .vibe-learn/session-log.jsonl.
---

# vibe-learn

Use this skill when the user asks to learn from the current coding session, understand what just happened, generate a session digest, quiz themselves on what was built, get a guided tour of a file or subsystem the session touched, save learnings to Obsidian, or recall related Obsidian notes from past sessions.

## Core Workflow

1. Locate the current project root from the conversation or working directory.
2. Read `.vibe-learn/session-log.jsonl` if present, plus `.vibe-learn/pause-summary.txt` when useful.
3. Ground explanations in the session log and any relevant files changed during the session.
4. If the log is missing or empty, say that vibe-learn has not captured events for this project yet and explain what can be inferred from available context.

## Briefing

In Learn Mode and Digest Mode, before anything else, refresh the session briefing: run `vibe-learn briefing --if-stale` via your shell tool. If `vibe-learn` is not on PATH, run `bash <dir>/briefing.sh --if-stale`, where `<dir>` is the directory that holds vibe-learn's `knowledge.sh` (`scripts/` in a full install, the hooks directory in a techpack install) (found with the knowledge-helper lookup; `~/.vibe-learn/scripts/` for a global install). It returns at once when the briefing is current. Skip it silently if neither exists, and do not mention its output unless it fails. In Digest Mode, after the last `touch`, run that refresh once more, so the session page lists the concepts just recorded; skip it when no concept was recorded.

## Learn Mode

When the user asks to "learn", explain recent activity in plain language:

- What changed
- Why the assistant likely made those choices
- Which files, commands, or patterns matter
- What the user can study next

If the user asks a specific question, answer that question first, then add only the session context needed to make it clear.

## Digest Mode

When the user asks for a "digest", produce a structured report:

- What Was Built
- Key Decisions
- Patterns Used
- Files And Commands Worth Reviewing
- Things To Study Next

Report a problem