I'm Urav. I build things with code.
This section auto-updates daily. It features one of my recent commits, or something interesting from my network, or a random gem from the wild. The commit gets roasted by an opinionated AI and rendered as a strange attractor.
Last updated: 2026-03-17
Commit: github/spec-kit by @pierluigilenoci Β· 9c0c144
Message: "fix(scripts): harden bash scripts β escape, compat, and error handling (#1869)
- fix(scripts): harden bash scripts with escape, compat, and cleanup fixes
- common.sh: complete RFC 8259 JSON escape (\b, \f, strip control chars)
- common.sh: distinguish python3 success-empty vs failure in resolve_template
- check-prerequisites.sh: escape doc names through json_escape in fallback path
- create-new-feature.sh: remove duplicate json_escape (already in common.sh)
- create-new-feature.sh: warn on stderr when spec template is not found
- update-agent-context.sh: move nested function to top-level for bash 3.2 compat
- fix(scripts): explicit resolve_template return code and best-effort agent updates
- common.sh: resolve_template now returns 1 when no template is found, making the "not found" case explicit instead of relying on empty stdout
- setup-plan.sh, create-new-feature.sh: add || true to resolve_template calls so set -e does not abort on missing templates (non-fatal)
- update-agent-context.sh: accumulate errors in update_all_existing_agents instead of silently discarding them β all agents are attempted and the composite result is returned, matching the PowerShell equivalent behavior
-
style(scripts): add clarifying comment in resolve_template preset branch
-
fix(scripts): wrap python3 call in if-condition to prevent set -e abort
Move the python3 command substitution in resolve_template into an if-condition so that a non-zero exit (e.g. invalid .registry JSON) does not abort the function under set -e. The fallback directory scan now executes as intended regardless of caller errexit settings.
- fix(scripts): track agent file existence before update and avoid top-level globals
- _update_if_new now records the path and sets _found_agent before calling update_agent_file, so that failures do not cause duplicate attempts on aliased paths (AMP/KIRO/BOB -> AGENTS_FILE) or false "no agent files found" fallback triggers
- Remove top-level initialisation of _updated_paths and _found_agent; they are now created exclusively inside update_all_existing_agents, keeping the script side-effect free when sourced"
Review: Bravo to the unsung hero battling shell script fragility and Bash 3.2 compatibility. From precise JSON escaping to explicit error handling and robust agent update logic, this is a meticulous effort to wrangle a chaotic environment into submission, one edge case at a time. This level of defensive programming in shell is both admirable and a strong indicator of past trauma.
Chaos: 70% Β· Mood: #4A6D8B
What is this?
The Pipeline:
- A GitHub Action runs daily and picks a commit (my own β network β starred repos β fallback)
- The commit diff is fed to Gemini, which produces a witty critique, a chaos score (0-100), and a mood color
- A Lorenz attractor is rendered using these parameters:
- Chaos score β modulates Ο (rho), affecting how chaotic the butterfly looks
- Mood color β tints the gradient from black β color β white
- Commit hash β seeds the initial conditions, so every commit is unique
The Math:
The Lorenz system is a set of differential equations that exhibit deterministic chaos. Small changes in initial conditions produce wildly different trajectories. It's the "butterfly effect", fitting for visualizing commits.
Links: