Bough — Development skill for Claude Code
Visualize your Claude Code session history as a diagram of the work you actually did: days, tasks, prompts and the commits that landed.
How to install Bough
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open nickelsec/bough and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Bough does
Visualize your Claude Code session history as a diagram of the work you actually did: days, tasks, prompts and the commits that landed. Local-first, single Go binary, nothing leaves your machine.
Alternatives in Development
- Spreadsheet — Create, edit, analyze, and visualize spreadsheets with formulas 14.6k ★
- Ralph Loop — Autonomous coding loop — works through tasks, commits, repeats 14k ★
- Claude Notifications Go — Cross-platform smart notifications -- 6 types, click-to-focus, context analysis, webhooks 365 ★
README
Read your Claude Code history and see the work you actually did.
Not how many tokens you burned or how long your streak is. Claude Code's own `/stats` covers that. This answers a different question: what did you actually build?
Run it
bough
That is the whole thing. It finds your projects, asks which one, and opens it in your browser.
What you get is a diagram of your own work. A square on the line is a day you sat down. Smaller squares hanging off it are the tasks inside that day. Every circle is a single prompt you typed.
Hover anything and the path back to its day lights up, with a note saying what it was. Click it and the full record opens beside the drawing, scrolled to the exact prompt, in your own words and untrimmed. Work that went badly is drawn in rust rather than green.
A task carrying a small mark is one that ended in a commit, and the note gives you the hash and the message. Everything else in the drawing is worked out from your history; this is the part you can go and check.
To get those right, bough also reads the git history of the project it is describing, at the path your transcripts already name. That is a read and nothing else: no writes
Related Skills
Agent Wrapped
A local-first wrapped card for how you actually work with Claude Code. Nothing leaves your machine.
Session Knowledge
Turn your Claude Code session history into a searchable local knowledge base — 13 MCP tools, pure stdlib, noth
Earheart
Talk to your coding agents — press a hotkey, speak your prompt, and it lands in Claude Code, Codex, or Cursor.
Kaectx
Local searchable store of your coding-agent sessions (Claude Code, Codex), served to any agent over MCP. Singl
Fable Countdown
Split-flap departure board counting down the days until Fable 5 leaves Claude subscription plans
Transcriptmeter
What your agent sessions cost, from the transcripts on your disk: tokens, cache hit ratio, peak context, list-
Related Agents
Entire Search
Search Entire checkpoint history and transcripts with entire search --json. Use proactively when the user asks
Visual Exporter
Convert a structured deepthinking thought into diagram source code. Use when the user asks to visualize, rende
Mermaid Flow Visualizer
Use this agent when the user explicitly requests a Mermaid diagram to visualize code architecture, data flow,