2 items
Collaborative file ordering in GitHub Pull Requests to improve code review efficiency Stop Fighting Alphabetical Order in Your Code Reviews GitHub forces you to review Pull Request files alphabetically, turning code review into a frustrating scavenger hunt. You jump between related files, lose context switching from tests to implementation and back, and waste mental energy reconstructing the logical flow of changes. For PRs with 20+ files, alphabetical ordering obscures dependencies and makes it nearly impossible to understand changes in a sensible sequence. PR File Reorder fixes this. Drag and drop files into the order that makes sense - dependencies first, core logic next, tests last. Share your preferred review sequence with your team, and our consensus algorithm automatically applies the best ordering when multiple reviewers contribute. Review PRs the way they should be reviewed: logically, efficiently, and collaboratively. Main Features: • Drag-and-Drop Reordering - Instantly reorganize PR files with an intuitive interface. Create the review sequence that matches how code should actually be understood. • Team Consensus - Share your file order with teammates via GitHub comments. When multiple reviewers suggest orderings, our algorithm merges them into one optimal sequence everyone sees. • Zero Infrastructure - No servers, no setup, no configuration. Orders are stored as GitHub comments using infrastructure you already have. Works entirely in your browser. • Always Editable - Orders are never locked. Any team member can update the sequence anytime. Democratic and flexible. • Privacy First - No data collection, no tracking, no external servers. Your preferences stay local. Shared orders are transparent GitHub comments.
Feb 19, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.