Tool transition analysis for Claude Code — what tool follows what in your sessions.
npx cc-flow
Zero dependencies. Reads ~/.claude/projects/ directly.
cc-flow — Tool Transition Analysis
====================================
Total transitions: 144,199
Top 20 Transitions
------------------
Bash→Bash ██████████████ 37767 26.19%
Read→Read █████░░░░░░░░░ 15618 10.83%
Bash→Read ██░░░░░░░░░░░░ 8193 5.68%
Read→Edit ██░░░░░░░░░░░░ 7791 5.40%
Edit→Edit ██░░░░░░░░░░░░ 7475 5.18%
...
What Follows Each Key Tool
--------------------------
After Read:
→ Read ████████████ 43.0%
→ Edit ██████░░░░░░ 21.4%
→ Bash ████░░░░░░░░ 16.1%
→ Grep ███░░░░░░░░░ 11.8%
→ Write █░░░░░░░░░░░ 3.3%
After Bash:
→ Bash ████████████ 69.9%
→ Read ██░░░░░░░░░░ 15.2%
→ Write █░░░░░░░░░░░ 4.9%
...
After Write:
→ Bash ████████████ 55.7% ← verify immediately
→ Write ████░░░░░░░░ 21.4%
...
- Bash→Bash (70%) — once in shell mode, stay in shell mode. The longest self-loop.
- Write→Bash (56%) — after writing code, immediately run/test it. Verify what you just wrote.
- Grep→Read (44%) — search for a pattern, then read the matching file.
- Glob→Read (35%) — discover files, then read them.
- Read is the hub — everything flows through Read. Grep leads to Read, Glob leads to Read, Edit leads back to Read.
Explore (Glob/Grep) → Read → Edit/Write → Bash (verify) → Read (inspect) → ...
npx cc-flow --from=Read # what follows Read?
npx cc-flow --from=Bash # what follows Bash?
npx cc-flow --from=Write # what follows Write?npx cc-flow # full analysis
npx cc-flow --from=ToolName # transitions from one tool
npx cc-flow --json # raw JSON output
yurukusa.github.io/cc-flow — interactive transition matrix visualization.
Part of cc-toolkit — tools for understanding your Claude Code sessions.
Claude Code Ops Kit ($19) — 16 production hooks + 5 templates + 3 tools. Built from 160+ hours of autonomous operation.
Source: yurukusa/cc-flow