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 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.
I ditched Emotion, a very similar solution, since it doesn't work with Next’s App Router, and while looking for a replacement (styleX, Griffel, Vanilla Extract…), I discovered that Styled-Components can be compatible with the App Router.
Why stick with Styled-Components? Because I want to write CSS, not JavaScript objects like most alternatives impose. I understand the typing advantages, but the readability loss just isn’t worth it.
I also use classNames, scoped to each component, it works fine. So why would I replace classNames with JavaScript constants? Again, proper CSS syntax is enough.
I was hoping YakJS would be a complete replacement for Styled-Components, but they don’t support classNames & global styles.
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.