Analysis updated 2026-05-18
Add a structured plan-then-build workflow to a Grok Build coding session.
Use a dedicated debugging command that follows a hypothesis-driven process.
Run an automated multi-step code review before shipping a change.
Clean up code that reads as obviously AI-generated.
| mitchellbernstein/lazygrok | 0xallam/my-recipe | 0xhassaan/nn-from-scratch | |
|---|---|---|---|
| Stars | 0 | — | 0 |
| Language | Python | Python | Python |
| Last pushed | — | 2022-11-22 | — |
| Maintenance | — | Dormant | — |
| Setup difficulty | easy | moderate | moderate |
| Complexity | 2/5 | 2/5 | 4/5 |
| Audience | developer | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires the Grok Build CLI and an already-authenticated Grok account.
LazyGrok is a plugin that adds a set of ready made workflows and helper agents to Grok Build, a command line coding assistant made by xAI. It brings over ideas from two earlier projects, oh my openagent and LazyCodex, which did something similar for other coding tools, and repackages them so they work with Grok instead. Once installed, LazyGrok gives you a family of slash commands that all start with the prefix lg, such as lg-ulw for an evidence driven build mode, lg-ulw-plan for turning a request into a written plan, lg-start-work for carrying out that plan, and lg-debug for hypothesis driven bug hunting. There are also commands for brainstorming ideas, reviewing finished work, cleaning up code that looks obviously AI generated, refactoring without changing behavior, and managing git commits. In total the plugin ships 28 skills plus a handful of shorter aliases so the same commands can be typed without the lg prefix. Alongside the slash commands, LazyGrok defines several specialized agents that Grok can call on for particular jobs: one that only reads and maps out a codebase, one that searches documentation and open source projects, workers that write code, and reviewers that check the work before it ships. Project state such as plans and brainstorm notes is kept in a folder called .omo inside whatever project you are working on. Installing it is a single command, grok plugin install mitchellbernstein/lazygrok --trust, followed by enabling the plugin in a config file and restarting the session. You need the Grok Build command line tool and a working Grok account already set up. The project is released under the MIT license, based on the earlier OmO and LazyCodex work, and as of this writing has no GitHub stars yet.
A Grok Build plugin that adds ready-made coding workflows, slash commands, and helper agents like planning, debugging, and code review.
Mainly Python. The stack also includes Python, Grok Build CLI.
MIT license: use, modify, and share freely, including commercially, as long as you keep the copyright notice.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.