git404hub

what is logbook fr?

promptwheel-ai/logbook — explained in plain English

Analysis updated 2026-05-18

3JavaScriptAudience · developerComplexity · 2/5Setup · easy

tl;dr

A single file, zero dependency CLI that mines a repo's git history into a compact brief AI coding agents can read before working on the code, so they know about reverted approaches and skipped tests.

vibe map

mindmap
  root((repo))
    What it does
      Mines git history
      Writes compact brief
      Tells the repo story
    Tech stack
      JavaScript
      Node.js
      npm package
    Use cases
      Brief fresh AI sessions
      Find hotspots and reverts
      Audit skipped tests
    Audience
      Developers using coding agents

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Give a fresh AI coding session context on past decisions before it starts editing an unfamiliar codebase

VIBE 2

Find out which parts of a repository have been rewritten or reverted the most

VIBE 3

Check what tests or warnings are currently being silenced in the codebase

VIBE 4

See a repository's history told back as a readable story instead of a raw commit list

what's the stack?

JavaScriptNode.jsnpm

how it stacks up fr

promptwheel-ai/logbookabhagsain/bayut-maps-ratingsabhishek-kumar09/who-is-imposter
Stars333
LanguageJavaScriptJavaScriptJavaScript
Last pushed2021-04-12
MaintenanceDormant
Setup difficultyeasymoderateeasy
Complexity2/52/53/5
Audiencedevelopergeneralgeneral

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · easy time til it works · 5min

One npx command with no dependencies or accounts needed, large repos just take longer on the first scan.

The README does not state a license.

in plain english

logbook is a command line tool that reads a project's entire git commit history and turns it into a short briefing document that AI coding assistants can read before they start working on the code. The idea is that fresh AI sessions usually only see the current code, not the story behind it: which parts were rewritten more than once, which approaches were tried and abandoned, or which test was quietly skipped last quarter. Reading every commit yourself would take too much space for an AI's context window, so logbook mines up to the most recent twenty thousand commits and compresses them into a compact record instead. Running one command scans the repository and writes three files. LOGBOOK.md is the short brief meant to be loaded directly into an AI assistant's instructions, covering frequently changed files, approaches that were reverted, and a list of times a test was skipped or a warning silenced. events.jsonl is a more detailed, one line per commit data file that other tools can query. JOURNEY.md tells the repository's history back as a narrative, viewable in color from the command line. The tool works entirely on your own machine. It never sends your source code or git history anywhere, and it only writes its own brief files, plus an optional block added to an existing agent configuration file such as CLAUDE.md so that future AI sessions are told to read the brief first. Scanning a large repository's full history is the slow part, but logbook caches the result so later runs only scan new commits, cutting a forty plus second scan down to a fraction of a second on a repeat run. A companion audit command shows what is still silenced in the current code, and a doctor command checks that the generated files and the agent wiring are still healthy. logbook has zero external dependencies and ships as a single file.

prompts (copy fr)

prompt 1
Run npx @promptwheel/logbook init in this repo and summarize what LOGBOOK.md found
prompt 2
Show me the do not retry entries in this repo's logbook before I try that approach again
prompt 3
Run logbook audit and tell me what is still suppressed in the current code
prompt 4
Generate the JOURNEY.md for this repo and tell me the most dramatic turning point

Frequently asked questions

what is logbook fr?

A single file, zero dependency CLI that mines a repo's git history into a compact brief AI coding agents can read before working on the code, so they know about reverted approaches and skipped tests.

What language is logbook written in?

Mainly JavaScript. The stack also includes JavaScript, Node.js, npm.

What license does logbook use?

The README does not state a license.

How hard is logbook to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is logbook for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.