31–39 of 39 posts
what's wrong with "git diff"?
AIs will make often make multiple "commits" worth of changes, and working out what's been done and why from a git diff is often quite hard.
My current workflow: I use GitHub web to look at my commits and leave inline comments on the lines. Then I have Claude Code fetch all the comments and apply the changes or answer my questions.
I don't always have multiple commitsn: sometimes it's just one big commit that I then ask the AI to split, and usually after a full review. I wouldn't say it's a common use case, but it's mine.
To give you an idea of how much I try to optimize this part of my work, I installed Stylus (a Chrome extension) to change GitHub's syntax highlighting colors, so I'm glad you've integrated something similar natively.
That said, with my big commits of several hundred or even thousands of lines, your Stage tool and the hosted version are unusable compared to GitHub web. I think improving performance should be a priority, probably through virtualization (windowing).
Another issue: I never open PRs. As I mentioned, I comment directly on my commits on a branch. PRs make sense for a team workflow, but I work solo.
You're solving a real problem, and despite beeing a bit broke ATM, I'd be willing to pay for a tool like this given the amount of time I spend on review. My current workflow: I use GitHub web to look at my commits and leave inline comments on the lines. Then I have Claude Code fetch all the comments and apply the changes or answer my questions. I don't always have multiple commitsn: sometimes it's just one big commit…