GitHits CLI

GitHits used to provide grounded examples of how something has been done before. Now it can also be used for more fine-grained discovery on code and documentation.

To install:

That one command detects your tools, walks you through login if you need an account, and configures the MCP server to work with your agent harnesses. No waitlist. Anyone can sign up now, either right from the CLI or from githits.com.

Your agent now gets 14 tools instead of 3. All new tools ship through the GitHits CLI.

Here's what we had before in the code example tool:

Natural-language query, returns a code example sourced from global open-source. Supports 800+ languages.

Discover supported languages for get_example and their canonical names.

Submit thumbs up or down for an example or in general for a session. Has also optional text feedback and tool name parameters.

Code Navigation consists of search and inspection tools.

1/ Code and Documentation Search for Open-Source

7 new tools for searching, grepping, listing, and reading code and docs in any open-source package.

Search across code, docs, and symbols in any package or GitHub repo. Supports discovery syntax with AND/OR, qualifiers (kind:, category:, path:, lang:), and scoped targets (npm:react, https://github.com/org/repo).

Deterministic text grep over indexed source files. Literal or regex, scoped by path/globs/extensions. Matches chain directly into code_read.

List files in any indexed dependency or repo. Filter by path prefix, globs, extensions, language, or file intent (production, test, example, etc.).

Read source files directly. Your agent can jump to exact line ranges from search or grep results. No cloning required.

List available documentation pages for a package (hosted + repo-backed).

Read a single doc page by pageId.

Poll the status of asynchronous indexing or search progress. Useful when an index is still being built.

GitHits indexes open-source packages fast (around 10 seconds for average repos and 2-5 minutes for large repos like Linux kernel) and makes code accessible to agents with sub-second queries.

20+ Supported languages: Bash, C#, C++, CSS, Dart, Elixir, Erlang, Go, Java, JavaScript, Kotlin, Lua, Markdown, PHP, Proto, Python, R, Ruby, Rust, Scala, SCSS, Swift, TypeScript, Zig. If you have a suggestion on what we should add next, let us know.

2/ Package Inspection

4 new tools for inspecting a package's metadata, dependencies, vulnerabilities, and changes.

Package overview (version, license, downloads, stars, recent changes).

Dependency graph analysis with transitive resolution and conflict detection.

Known vulnerability check with severity filtering.

Release notes, newest-first, with range queries.

Package Inspection supports 11 registries: npm, pypi, hex, crates, vcpkg, zig, nuget, maven, packagist, rubygems, go. If you have a suggestion on what we should add next, let us know.

Before this update, GitHits answered one question for your agent: "How has this been done before?" The agent got real implementations distilled from open-source code.

That worked for common patterns. It left a gap when the answer required understanding how a package actually works internally: which functions exist, which calls what, and how a specific version handles an edge case.

For that, your agent fell back on web searches and GitHub reads, usually pulling code from main instead of the version you've actually installed. That's how you get invented APIs, confidently wrong fixes, and retry loops.

This update closes that gap. Your agent can now navigate any indexed package's source on demand. Read source files at exact line ranges, grep across a dependency, inspect transitive deps, check vulnerabilities, follow changelogs. Correctly versioned against what you've installed. No cloning required.

Together with the existing example pipeline, your agent now has both halves of the picture: how something has been done before, and how the code you're working with actually works.

Feedback welcome. Open an issue on GitHub or drop a message in our GitHits Community Group.

Ask your agent to use GitHits to explore https://github.com/postgres/postgres and explain how the query planner selects join strategies. It'll search the codebase, read the relevant source files, and walk you through the answer without cloning anything.

Some of the features we're building:

Provide call graph for the symbol allowing agents to quickly understand flow through functions cross-packages

Allow agents to see what really changed between the versions and not just what is written to change logs

➜ Which of these would bring the most value for you? Or something else? Tell us!

Baseline Skill Template

Several of you have asked for a starter skill that teaches agents how to use GitHits tools without writing your own prompt instructions. We're working on it.