Skip to content
View urav06's full-sized avatar
  • Melbourne, Australia
  • 08:38 (UTC +10:00)

Highlights

  • Pro

Block or report urav06

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
urav06/README.md

Hey πŸ‘‹

I'm Urav. I build things with code.


πŸ“Œ Featured Commit

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-04-25

Entropy

Commit: github/spec-kit by @mnriem Β· 171b65a

Message: "docs: replace deprecated --ai flag with --integration in all documentation (#2359)

  • docs: replace deprecated --ai flag with --integration in all documentation

Replace all user-facing --ai, --ai-skills, and --ai-commands-dir references with their modern equivalents:

  • --ai β†’ --integration
  • --ai-skills β†’ --integration-options="--skills"
  • --ai-commands-dir β†’ --integration generic --integration-options="--commands-dir "

Updated files:

  • README.md (~17 occurrences)
  • docs/installation.md (~8 occurrences)
  • docs/upgrade.md (~11 occurrences)
  • docs/local-development.md (~5 occurrences)
  • CONTRIBUTING.md (1 occurrence)
  • extensions/EXTENSION-USER-GUIDE.md (1 occurrence)
  • src/specify_cli/init.py (docstring examples and error messages)

Left unchanged:

  • CHANGELOG.md (historical record)
  • Test files (intentionally exercise deprecated flag path)
  • CLI flag implementation (backward compatibility)

Closes #2358

  • docs: address review feedback on pre-existing issues
  • Fix duplicate copilot example in README.md (replace with codex)
  • Fix invalid gemini --integration-options="--skills" example (gemini does not support --skills)
  • Update generic integration comment from 'Unsupported agent' to 'Bring your own agent; requires --commands-dir'
  • Clarify EXTENSION-USER-GUIDE.md: skills auto-register for skills-based integrations, not only with --integration-options
  • docs: replace bare 'AI agent' / 'AI assistant' with 'coding agent' throughout

Full sweep across all documentation and user-facing CLI messages to align terminology. Bare references like 'AI agent', 'AI assistant', and 'AI Agent' are replaced with 'coding agent' or 'coding agent integration' as appropriate.

Intentionally left unchanged:

  • 'AI coding agent' (already correct expanded form)
  • Deprecated --ai flag help text and error messages (describes the deprecated flag itself)
  • Community extension descriptions (external project text)
  • 'generated by an AI' in CONTRIBUTING.md (general AI, not agent)
  • docs: address review β€” remove deprecated --offline, qualify --skills scope
  • Remove --offline from docstring examples (deprecated no-op)
  • Remove --offline from CONTRIBUTING.md testing example
  • Replace --offline instructions in docs/installation.md with note that bundled assets are used by default
  • Qualify --integration-options="--skills" in README.md to note it only applies to integrations that support skills mode"

Review: Ah, the grand "docs" change that's really a total rewiring of how users talk to the tool. Replacing every single 'AI agent' with 'coding agent' smells like a marketing directive, and deprecating direct flags for quoted integration-options feels like a regression in usability. It's a thorough clean-up, I'll grant you that, but also a stark monument to early API indecision.

Chaos: 75% Β· Mood: #4682B4


What is this?

The Pipeline:

  1. A GitHub Action runs daily and picks a commit (my own β†’ network β†’ starred repos β†’ fallback)
  2. The commit diff is fed to Gemini, which produces a witty critique, a chaos score (0-100), and a mood color
  3. 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:

Browse the museum β†’ Β· See the code β†’

Pinned Loading

  1. claudestrophobic claudestrophobic Public

    Brings conversation management back.

    Python 6

  2. dialectic dialectic Public

    A Rebuttal Engine for Computational Argumentation in Claude Code CLI

    Python 6

  3. career-gradient-descent/content-optimizer career-gradient-descent/content-optimizer Public

    Content engine to minimize the loss function of job applications.

    Jinja 1 2

  4. blitz-chess blitz-chess Public

    World's Fastest Chess Engine (Coming Soon)

    Rust

  5. research research Public

    The Meta-Learning Gap: Combining Hydra & Quant for Large-Scale Time Series Classification

    Python