←back to thread

262 points lawrencechen | 6 comments | | HN request time: 0.583s | source | bottom

0github.com is a pull request viewer that color-codes every diff line/token by how much human attention it probably needs. Unlike PR-review bots, we try to flag not just by "is it a bug?" but by "is it worth a second look?" (examples: hard-coded secret, weird crypto mode, gnarly logic, ugly code).

To try it, replace github.com with 0github.com in any pull-request URL. Under the hood, we split the PR into individual files, and for each file, we ask an LLM to annotate each line with a data structure that we parse into a colored heatmap.

Examples:

https://0github.com/manaflow-ai/cmux/pull/666

https://0github.com/stack-auth/stack-auth/pull/988

https://0github.com/tinygrad/tinygrad/pull/12995

https://0github.com/simonw/datasette/pull/2548

Notice how all the example links have a 0 prepended before github.com. This navigates you to our custom diff viewer where we handle the same URL path parameters as github.com. Darker yellows indicate that an area might require more investigation. Hover on the highlights to see the LLM's explanation. There's also a slider on the top left to adjust the "should review" threshold.

Repo (MIT license): https://github.com/manaflow-ai/cmux

1. mattfrommars ◴[] No.45767066[source]
Can someone please explain to me how do people build these kind of tools? My background is classic Java/C# backend development and SQL. A bit microservice using Spring Boot. Its 8:30pm and I'm watching React tutorials to understand better how modern websites are built - e.g. use useState, useRef etc.

Now, how does any of my experience translate to building tools like cmux? I genuinely want to understand how.

Is the answer to go line by line of cmux code base or make an attempt to open a PR on one of the bugs issues on cmux and, by magic and time, I will eventually understand?

replies(5): >>45767203 #>>45767228 #>>45767295 #>>45769017 #>>45773431 #
2. rahimnathwani ◴[] No.45767203[source]
What would you recommend to someone new in your team who had only ever used python and a bit of SQL, and had never touched Java or Spring Boot?
3. joshribakoff ◴[] No.45767228[source]
High level: hit github api, feed code to llm, display results in web app.

If you want to learn web apps start with the docs, eg. Official react docs or even just learning vanilla JavaScript if you don’t know it.

Start with little pieces like hitting the github API and displaying some json in the terminal

You could also just start prompting an llm to scaffold a project for you and then trying to debug whatever issues come up (and they will)

4. lawrencechen ◴[] No.45767295[source]
If your goal is to make something useful, I think the fastest way is probably to build a CLI only version since you can theoretically render heatmaps and make a task manager in a CLI form factor. And your background in Java/C# helps here.

Use Claude Code or Codex for everything, learn how to prompt well. >90% of cmux and 0github.com was written by LLMs. Most of it was just me asking the LLM to implement something, testing it to see if it works, and if it doesn't, I'll ask the LLM to write logs, and I'll paste the logs back to the LLM. Ask gpt-5-pro for architecture choices, like what tech/dependencies to use.

But if your goal is to learn React, I'd recommend going through the official getting started documentation, it's pretty good.

5. rf15 ◴[] No.45769017[source]
Your experience in coding is enough, you need more practice in "problem solving" with crazy ideas and working through them to the finish line.

Besides, this is just a thin layer on an LLM, with questionable actual quality. Learn to do the real work, no magic machine can take learning and skill building off your shoulders.

6. rs186 ◴[] No.45773431[source]
I suggest that you ask Claude Code to build such a website for you with a minimal set of features, with tons and tons of comments and design/architecture documents plus tests. Once that is done, you can start reading the code. You can even read as it is working.

Then, you can point Claude Code to a file/a function/a few lines and ask follow-up questions.

After that, there are even more things to do. If you want a different perspective, you could try completely reimplementing the thing. My guess is that Claude will use Next.js. You can ask Claude not to do that but instead use a different UI framework/no framework combined with C#, if that's something you are interested in. If you want to actually learn all the details, you can start setting things up yourself and write the website. You can add features or try making the site scalable, under AI-assisted or vibe coding mode.

It will not produce the most elegant code or have the best architecture, but will be good enough for your purpose. I think it's the most efficient way to get some learning that is specifically suited to your needs in this age.