Live data from Hacker News

Show HN: Stage CLI – An easier way of reading your AI generated changes locally

github.com

21–30 of 39 posts

Re: Show HN: Stage CLI – An easier way of reading your AI generated changes locally

#21
post #20

This looks useful. With AI generated code the hardest part is reviewing it. A normal git diff gets messy once the agent changes several files for different reasons. Grouping the change into “chapters” seems like the right idea. Do you infer those chapters only from the diff, or can you also use the agent’s original plan/task history?

the cool part is that you can run the skill from the same agent session so it has the context on the plan and implementation process

but if you run the skill in a fresh session, it naturally wouldn't have the plan

Re: Show HN: Stage CLI – An easier way of reading your AI generated changes locally

#22
post #18

Interested to try this! Have you thought about separating the parts of a PR that are routine/uninteresting from the parts that are load-bearing and need more careful review?

yes! we've found that reading changes this way make it very easy to separate the important stuff from the unimportant stuff, and we're thinking of ways to make that more visible in the UI

Cool, good to hear. I think it’s often the case even within an individual file or change that it’s 90% routine and 10% critical to review. That’s a big part of the problem in my mind.

Re: Show HN: Stage CLI – An easier way of reading your AI generated changes locally

#25

Minor nitpick: This isn't what I expected when I read "CLI". I envisioned a terminal-native experience. Unless I skimmed over this way too fast, this is a browser experience that you trigger from the terminal. EDIT: I should mention that I think the idea is cool. We're in a new age where reviewing large amounts of unfamiliar code has become a larger problem than it was previously.

If you do want a native CLI in-terminal for this, try out github.com/agavra/tuicr
Post reply on HN