Turning 105 Session Logs into Build Logs: A Claude Code Automation Pipeline

I had 105 Claude Code session logs sitting in .jsonl files. Writing build logs meant opening each one, extracting the interesting parts, and assembling them into coherent posts. I never got around to it. So I built an automation pipeline instead. It handles session parsing, build log generation via Claude CLI, git push, and Cloudflare deployment in one pass. TL;DR : I built a pipeline that parses Claude Code .jsonl sessions and auto-generates build logs using the Claude CLI. The raw material was always there -- the reason I never wrote those posts was laziness, not lack of content. Every Build Log Ingredient Was Already in the Session .jsonl Files Claude Code stores project sessions under ~/.claude/projects/ as .jsonl files. Each line contains a single message as JSON: user prompts, Claude's responses, tool call results, and timestamps. Parse these files and you get "who asked what, which tools Claude used and how many times, and which files were touched." Everything a build log needs