COMPARISON

RepoKit search vs. GitHub's built-in file finder

GitHub's own "press t to search files" feature is genuinely good and RepoKit isn't trying to replace it — it's a second, complementary way to get around a repo fast, with different information attached to each result.

GitHub's file finder, and what it's good at

Press t anywhere on a GitHub repository and a fast, fuzzy file-search box appears — GitHub's own team built this, and it's reliable, fast, and requires no extension at all. For pure "jump to this filename" navigation, it does the job well.

What RepoKit's search adds

RepoKit's search (Ctrl/Cmd+Shift+K) is a separate tool that layers in information GitHub's finder doesn't show: each result includes the file's size, and if a filename is duplicated elsewhere in the repo, that's flagged directly in the results list rather than requiring a second lookup. It's built on the same tree data RepoKit already loads for its size badges, so there's genuinely no extra cost to having both running.

GitHub's 't' finderRepoKit
ShortcuttCtrl/Cmd+Shift+K
Requires installing anythingNo — built into GitHubYes — the RepoKit extension
Shows file size in resultsNoYes
Flags duplicate filenames in resultsNoYes
Works without an extensionYesNo
Search speedFastFast — same underlying data RepoKit already indexed

Use both — they don't conflict

Since the shortcuts are different and neither tool interferes with the other, there's no real reason to pick just one. Reach for t when you just need the filename fast; reach for RepoKit's search when the size or duplicate context is useful too.

Frequently asked questions

Should I disable one to use the other?+
No — they work fine side by side. GitHub's finder is triggered with 't', RepoKit's with Ctrl/Cmd+Shift+K, so there's no conflict, and you can reach for whichever fits the moment.
Why did you build a search feature if GitHub already has one?+
Because RepoKit's search is tied into the rest of its data — size and duplicate information appear directly in results — which GitHub's own finder, reasonably, doesn't attempt since it's a general navigation tool, not a repo-analysis one.
Keep exploring

Related pages

Get size and duplicate context in every search result.

RepoKit's search adds detail GitHub's built-in finder doesn't show.

Add RepoKit to Chrome — it's free
Free · No account required · Works instantly on github.com