wtf is vibediary?

Vibediary turns your Claude Code coding sessions into a plain English project diary, using one command and no separate API keys. The idea behind it is that after months of AI assisted coding, a developer can end up with working code they no longer understand, since the AI wrote much of it. The code shows what was built, but the reasoning behind decisions, what was asked for, what broke, and why things turned out a certain way, usually disappears the moment a terminal is closed. Vibediary reads through your Claude Code session transcripts and writes that missing story down in beginner friendly language. To use it, you clone the repository into your Claude Code skills folder, then run a single slash command inside any project. This produces three files in a docs folder: a dated diary of what got built and why, a living explanation of how the whole project works that stays current on each run, and a visual, hoverable map of the project where each part shows a simple explanation of what it does. Two safety measures are built in. The generated folder starts out excluded from version control by default, so the diary will not accidentally get committed until you choose to include it, and if a project already has its own docs folder for something else, vibediary writes into a separate subfolder instead of touching existing files. There is also an optional automatic mode that runs the diary update whenever a Claude Code session ends, set up through a short snippet in the project's settings file. Each automatic run is a real Claude session and uses tokens from your plan, so the author suggests running the command by hand if you close sessions frequently. The tool only works with Claude Code sessions, cannot see changes made outside those sessions, and since it repeats what you typed, private information mentioned in a session could end up in the generated diary. It is released under the MIT license.