That's how I code nowadays:
1. Start a session.
2. Grill my requirements.
3. Write an ADR, then either start implementing or separate into pieces.
4. Review the code on pyor.review, compared to Github, Pyor allows me to categorize the files and changes then review the important stuff and skim the noise it identifies.
5. Since I can do local reviews with Pyor, I can do that with Claude and feed back my comments to be addressed without it going to Github first.
6. Create a PR then merge it.
(user othmanosx owns pyor)
whats the catch on pyor, how is it free?
it's a wrapper around GitHub APIs. Github is still the BE, Pyor is only the better UI
Based on your comment, I assume you use Matt Pocock’s skills, is that correct?
If so, have you compared it to obra’s superpowers?
YES! and I already love them. haven't heard of obra’s superpowers, will check them out. Thanks.