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 ██████░░░░ 68 · Mood
github/spec-kit by @mnriem · bbe8631
feat(cli): add `py` script type & Python interpreter resolution (#3278) (#3285)
* feat(cli): add `py` script type & Python interpreter resolution (#3278)
Introduce a third script variant alongside `sh`/`ps` as the foundation
for unifying workflow s
…
This is a seriously impressive dive into the often-nightmarish world of cross-platform Python invocation. The logic for finding interpreters—from venvs to PATH to sys.executable, all while wrangling Windows paths and executable bits—shows a deep, albeit painful, understanding of real-world portability issues. The level of detail here is a stark reminder that even a 'simple' feature addition can hide a thousand dragons.
captured 2026-07-02
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.