Hello, riff
riff has a home on the web: docs for the app and the command line, and a blog for what comes next.
riff started as a faster way to read a diff. It grew into the place I do code review: the PRs that need me, ranked by what I have to do about them; the change itself, with viewed marks and a view of only what changed since my last pass; drafts that sync to my pending GitHub review; an agent sidebar that can rework those drafts; and a command line that answers “what needs me?” without opening a browser.
Until now all of that was documented in a README and a long cli.md. This site replaces both.
What’s here
- Docs for the desktop app, the browser version and the command line, plus a full configuration reference.
- This blog, for release notes, design notes and the reasoning behind how riff works.
What riff believes
A review tool should help you spend attention, not just display text. riff remembers what you’ve read and shows you what changed since, so a second pass costs minutes, not an hour. It ranks your PR inbox by the next action, not by date. And when a model helps, it prepares drafts for you to edit; it never submits a review on your behalf.
What’s next
Posts here will cover how the inbox decides what needs you, how the Story order of a PR’s files is built, and how stacked PRs and Jira dependencies come together into a merge order. Subscribe with RSS.