github-code-searchSearch GitHub code across your org

Search up to 1,000 results across every repo. Group by team. Triage interactively. Export to Markdown or JSON.

Org-wide code search

Search across all repositories in a GitHub organisation in a single command. Results are paginated automatically — up to 1,000 items.

Per-repository aggregation

Results are grouped by repository, not shown as a flat list. Fold or unfold each repo to focus on what matters.

Keyboard-driven TUI

Navigate with arrow keys, select individual extracts, filter by file path, and confirm with Enter — all without leaving the terminal.

Fine-grained selection

Pick exactly the repos and code extracts you want. Deselected items are recorded as exclusions in the replay command.

Structured output

Get clean Markdown lists with GitHub links, or machine-readable JSON — ready to paste into docs, issues or scripts.

Replay command

Every interactive session produces a one-liner you can run in CI to reproduce the exact same selection without the UI.

Get up and running in 30 seconds

One command. Auto-detects your OS and architecture.
Works on macOS, Linux, and Windows (Git Bash / MSYS2).

Works with

zshbashfishmacOSLinuxWindows GitHub Actions

Step 1: Install the binary

$ curl -fsSL https://raw.githubusercontent.com/fulll/github-code-search/main/install.sh | bash

Step 2: Export your GitHub token

Requires a GitHub token with repo scope (read-only). Generate one ↗

$ export GITHUB_TOKEN=ghp_your_token_here

Step 3: Run your first search

$ github-code-search query "TODO" --org my-org

How it works

From query to structured output in three steps.

Step 1

Search across the org

Run a single command. GitHub Code Search API is called automatically and results are paginated — up to 1 000 results across all repositories in your organisation.

Step 2

Triage interactively

A keyboard-driven TUI opens. Navigate repos, expand extracts, filter by file path. Select exactly what matters — deselect noise. Works without leaving the terminal.

Step 3

Export & replay

Press Enter. Get clean Markdown with GitHub links, or machine-readable JSON. A replay command is printed — paste it into CI to reproduce the exact selection non-interactively.

Use cases

Which repos still import lodash?

See every repository still importing a given library. Select the ones to migrate and get a Markdown checklist to paste directly into your migration issue.

bash

$ github-code-search query "from 'lodash'" --org my-org

Why not `gh search code`?

The official gh CLI supports gh search code, but returns a flat paginated list — one result per line, no grouping, no interactive selection, no structured output. github-code-search is purpose-built for org-wide code audits and interactive triage.

Feature comparison between gh search code and github-code-search
	gh search codegh search	github-code-searchgcsPurpose-built
Results grouped by repositoryOne block per repo instead of a flat list — fold or unfold at a glance.
Interactive TUI — navigate, select, filterArrow-key navigation, path-based filter and live selection without leaving the terminal.
Fine-grained extract selectionCherry-pick individual code extracts; deselected items become —exclude flags automatically.
Markdown / JSON outputExport clean Markdown checklists or machine-readable JSON ready for CI scripts.
Replay / CI commandEvery session produces a one-liner to reproduce the exact output headlessly in CI.
Team-prefix groupingCluster repos by GitHub team prefix (squad-, chapter-) for org-wide triage.
Syntax highlighting in terminalLanguage-aware token colouring rendered in the TUI — no browser needed.
Pagination (up to 1 000 results)Both tools auto-paginate the GitHub search API — up to 1 000 results per query.

What people say

Trusted by engineering teams who live in the terminal.

We use it weekly to track down deprecated patterns spread across 200+ repos. What used to take hours of grepping now takes minutes — and the replay command is gold for CI.
Platform EngineerSeries B tech company · 40+ repos

The per-repo grouping is exactly what was missing from gh search code. I can instantly see which teams own the code I'm looking at without context-switching to GitHub.
Staff EngineerEngineering org · 120+ repos

We pipe the JSON output into our internal tooling to generate automated refactoring tickets. The non-interactive mode with --output-type json is a hidden gem.
DevOps LeadInfrastructure team · 30+ repos

Using github-code-search in your org?
We'd love to hear your experience.