This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
CodeSloth
Review big GitHub PRs in a sensible order
CodeSloth turns a big GitHub pull request into ordered review steps: contracts first, then core code, the code that uses it, tests, and lockfiles last. Each step says why it comes now, and risky changes get flagged. No AI, read-only, runs locally.
CodeSloth is for the moment you open a 36-file PR and your brain quietly types "LGTM".
It reads the PR and turns it into a short checklist of ordered steps: contracts and schemas first, then the core code, then the code that uses it, then tests, config and lockfiles. Each step has one line on why it comes now ("5 other changed files import this."), worked out from a real import graph for JS/TS, React, Vue, Go and Python.
It also:
walks you file by file with "Mark file as reviewed & next" and n / p / j / k shortcuts
turns your ticks amber when new commits change a file you already reviewed
flags changes that break after the tests pass: dropped columns, edited migrations, removed routes or config keys
draws a dependency graph of the changed files and shows each file's commit history
No AI and no server. It uses a read-only GitHub token that stays in your browser and only makes GET requests to api.github.com. "Try demo" in the panel works without a token.
I'd love to hear where the ordering gets it wrong on your PRs.
About CodeSloth on Product Hunt
“Review big GitHub PRs in a sensible order”
CodeSloth was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #111 on the daily leaderboard. CodeSloth turns a big GitHub pull request into ordered review steps: contracts first, then core code, the code that uses it, tests, and lockfiles last. Each step says why it comes now, and risky changes get flagged. No AI, read-only, runs locally.
On the analytics side, CodeSloth competes within Chrome Extensions, Developer Tools and GitHub — topics that collectively have 617.6k followers on Product Hunt. The dashboard above tracks how CodeSloth performed against the three products that launched closest to it on the same day.
Who hunted CodeSloth?
CodeSloth was hunted by Yash Verma. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of CodeSloth including community comment highlights and product details, visit the product overview.
Hey Product Hunt 👋
CodeSloth is for the moment you open a 36-file PR and your brain quietly types "LGTM".
It reads the PR and turns it into a short checklist of ordered steps: contracts and schemas first, then the core code, then the code that uses it, then tests, config and lockfiles. Each step has one line on why it comes now ("5 other changed files import this."), worked out from a real import graph for JS/TS, React, Vue, Go and Python.
It also:
walks you file by file with "Mark file as reviewed & next" and n / p / j / k shortcuts
turns your ticks amber when new commits change a file you already reviewed
flags changes that break after the tests pass: dropped columns, edited migrations, removed routes or config keys
draws a dependency graph of the changed files and shows each file's commit history
No AI and no server. It uses a read-only GitHub token that stays in your browser and only makes GET requests to api.github.com. "Try demo" in the panel works without a token.
I'd love to hear where the ordering gets it wrong on your PRs.