/builds/vibe-check
// damage meters for AI-assisted development
In WoW, I ran damage meters obsessively: DPS, interrupts, and deaths for every M+ run. You can't improve what you can't measure.
vibe-check does the same thing for AI-assisted coding sessions. It analyzes git history and tells you if that session was actually productive or just busy.
// the 5 core metrics
How tight are feedback loops?
Building or debugging?
Does code stick?
How long stuck?
What % productive?
Trust Pass Rate is THE key metric—it measures whether you vibed at the right level.
npx @boshu2/vibe-check// the insight
Git history doesn't lie. It's easy to feel productive, but are you actually shipping or just spinning? The commits tell the truth.
vibe-check analyzes your commit patterns to detect debug spirals before they consume your whole session. If you're stuck for 30 minutes on the same thing, that's a wipe—reset, do some research, and come back with a plan.
"Last week, the CLI flagged a spiral at 18 minutes. I realized I was arguing with the LLM about a circular dependency. I stepped away, drew the schema on paper, and fixed it in one commit. Without the alert, I would have wasted two hours."
// part of the ecosystem
vibe-check is the MEASURE layer of a complete system. It provides the feedback loop that makes everything else work.
See full ecosystem →