I'm Urav. I build things with code.
Every day a bot grabs a commit (one of mine, someone I follow, or a stranger's), an AI names and roasts it, and it ends up as a strange attractor.
Chaos ██████░░░░ 65 · Mood
affaan-m/ECC by @affaan-m · 64cd1ba
fix: surface warn-only PreToolUse hooks (#2084)
This is a brilliant architectural decision, moving 'warn-only' output from the chaotic mess of stderr to structured JSON on stdout. It untangles the output streams beautifully, making programmatic consumption of hook warnings reliable and clear. Centralizing this output mechanism with pretooluse-visible-output is pure genius; it feels like untangling a particularly stubborn knot with surgical precision.
captured 2026-05-31
What is this?
flowchart LR
commit["🌌 daily commit"] -->|diff| gemini["Gemini"]
gemini -->|chaos + mood| attractor["Lorenz attractor"]
gemini -->|title + roast| exhibit["today's exhibit"]
attractor --> exhibit
A GitHub Action runs daily and picks a commit: mine if I've pushed recently, otherwise something from my network or a starred repo, and the Linux genesis commit as a last resort. Gemini gives it a name, a roast, a chaos score (0-100), and a mood color. Those become a Lorenz attractor: chaos controls how wild the butterfly gets, mood tints the gradient, and the commit hash sets the starting point. The math is identical every run, so the commit is the only thing that changes the picture.