# Code Navigation: Give Your Agent Real Access to the Source > Source: > Published: 2026-06-10 00:00:00+00:00 [Back to blog](/blog/) June 10, 2026 · 2 min read # Code Navigation: Give Your Agent Real Access to the Source A new code navigation skill gives your agent search, file listing, read, and grep across a codebase, so its answers come from the actual code. When an agent answers from memory, it can miss the implementation details that actually matter. Code navigation gives the agent a better path: search the code, list files, read exact source, and grep for the terms it needs. The answer comes from the codebase, not a remembered summary. ## Install the skill Run the GitHits init flow: ``` npx githits@latest init ``` Choose the agent skills path, then install ** githits-code**. That skill teaches your agent when to use GitHits for code and documentation navigation instead of relying on generic web context. ## What `githits-code` gives your agent The skill gives your agent a workflow for moving through source code deliberately. Search finds relevant code, docs, and symbols. Code files shows what lives under a path such as `src` . Code read opens the exact file and line range. Code grep finds deterministic text or regex matches across indexed source. Used together, those tools let the agent explore an open-source project without cloning it and without guessing which files matter. ## Example: why Hono’s router is fast In the walkthrough, the agent investigates Hono’s `RegExpRouter` . Instead of answering from general knowledge, it searches the Hono repo, reads the relevant router code, and follows the implementation. The source shows the important detail: `RegExpRouter` compiles routes into a large regular expression, matches once per request, then uses the result to index into route data. That avoids checking every route one by one on each request. ## Source-grounded answers The useful part is not only the explanation. It is the trail behind it. The agent can point to the files and lines it used, so you can verify the answer before you build on it. Try ** githits-code** when you need to understand how a library works internally, why an API behaves a certain way, or where a behavior is implemented. ## Try these prompts After installing the skill with `npx githits@latest init` , try prompts like: - “Use GitHits to explore [https://github.com/honojs/hono](https://github.com/honojs/hono)and explain how RegExpRouter matches routes.” - “Use GitHits to find where FastAPI registers routes and cite the files you read.” - “Use GitHits to inspect the React repo and explain how `useState` is exported.” - “Use GitHits to grep for the error message in this stack trace and read the implementation around it.”