This started as a weekend hack — but the idea’s been rattling around in my head for two years. I’ve always felt like PRs and code reviews are kinda broken. They get rubber-stamped, not because people don’t care — but because they’re too big, too vague, and too hard to follow. You never really know: – How long is this gonna take me to review? – What problem are we even solving here? – Why is there 100 files changed for fixing a bug? Oh something got renamed and now I have to hunt for the ACTUAL change. So I built CodeStory to help with that. Quick summaries, estimated reading time, and better context — all meant to make PRs something you actually want to read. Would love to hear what you think. Especially what sucks or what’s missing. This will work best for a team, so would love to find some small teams struggling with this issue who would be game to explore with me. Thanks for checking it out. - Elliott

Code Story

Transform pull requests into engaging stories

Transform pull requests into engaging stories