We got a lot of great feedback but also heard from many people that they wanted to have the chapters experience even before opening a PR… so we built the Stage CLI as the local, open-source version that anyone can try.
Here’s a quick demo video: https://www.tella.tv/video/stage-cli-demo-f55q
It works with any coding agent of your choice. The skill instructs the agent to read your current branch’s changes, break them down into separate logical chapters, and open them in a local browser.
We’ve found that reading changes this way is a lot easier for us than reading them in an IDE or other similar CLI tools, which present diffs to you in repository tree order. You can see a few examples of what it feels like here: https://stagereview.app/explore.
Try it out and let us know what you think! Would love to hear any feedback :)
mkw5053•1h ago
I've been spending a lot of my energy lately on how to run eng teams where we:
1. Maximize long-term shipping velocity
2. Maximize quality (whatever that means)
3. Maintain minimal complexity
4. Are intentional about which skills we let atrophy, which we keep sharp, and which new ones we have to build
5. Make juniors more capable, not just more productive
These are always in tension.
I've been thinking about instituting some sort of socratic method during planning and review plus spaced interval testing to ensure both the humans and AI coding agents understand and find some max of the factors above.
cpan22•58m ago
And yeah, I think number 5 on your list is particularly interesting - juniors will develop much slower if they don't go through the struggle of understanding implementation
We're hoping that our tool can help make that easier