Big PRs in older codebases are where production bugs slip through review. GitHub lists the changed files alphabetically, so you read a handler before its types, the tests before the code they test, and the migration somewhere in the middle. Thirty files in, "LGTM" gets very tempting. CodeSloth is a free Chrome extension that turns a pull request into a short checklist you can read like a story: contracts and schemas the core code everything else imports the code that uses it tests, config and the lockfile last Each step has one line on why it comes now ("5 other changed files import this."), so you know what to read closely and what to skim. It also: - flags changes that break after the tests pass: a dropped column, an edit to a migration that's already merged, a removed route, or a config key the code still reads - takes you file by file with "Mark file as reviewed & next" (n/p/j/k on the keyboard) - turns a tick amber if a new commit changes a file you already reviewed - shows each file's commit history and a dependency graph of the changed files There's no AI in it. The order comes from a real import graph for JS/TS, React, Vue, Go and Python, and the risk flags are plain rules, so the same PR always gets the same steps. It uses a read-only GitHub token that stays in your browser, there's no server, and "Try demo" works without a token. Chrome Web Store: https://chromewebstore.google.com/detail/bklcbahnfcmbjghhalbmihabampdlpdg 21-second video: https://www.youtube.com/watch?v=4XZh1rNLQ9c I'd love to hear where the ordering gets it wrong on your PRs, and which languages or frameworks you'd want next.   submitted by   /u/wanderer_2110 [link]   [comments]